Dynamic User Interface Schemes for an Electronic Device Based on Detected Accessory Devices

ABSTRACT

A method includes, at a computer system with a display, a housing, and an attachment mechanism, detecting attachment of an accessory to the computer system, where the accessory, while attached, has a predetermined orientation relative to the attachment mechanism, and in response to detecting the attachment of the accessory to the computer system in accordance with a determination that the accessory is a first accessory with first physical dimensions, displaying, on the display, a first visual indication that the accessory has been attached to the computer system, wherein the first visual indication indicates at least one property of the first physical dimensions, and in accordance with a determination that the accessory is a second accessory with second physical dimensions that are different from the first physical dimensions, displaying, on the display a second visual indication that the accessory has been attached to the computer system, wherein the second visual indication indicates at least one property of the second physical dimensions and the second visual indication is different from the first visual indication.

FIELD

The described embodiments relate generally to electronic devices, andmore particularly to electronic devices and accessories that usenear-field wireless communication systems to dynamically alter theoperation of the electronic devices.

BACKGROUND

Handheld electronic devices such as mobile phones and tablet computersprovide numerous functions and features, and use graphical userinterfaces to allow users to interact with and control those functionsand features. For example, handheld electronic devices display inputobjects such as icons, buttons, keys, and other graphical objects withwhich a user may interact to control the devices and their variousfunctions. The devices may also display output objects, such as text orimages, that convey information to the user.

SUMMARY

A system may include an electronic device that includes an enclosurehaving a transparent cover. The electronic device may also include adisplay positioned below the transparent cover and configured to displaya first graphical output and a second graphical output different fromthe first graphical output, and a touch sensor positioned below thetransparent cover and configured to detect touch inputs applied to thetransparent cover. The system may also include a protective case thatincludes a shell defining a cavity and configured to at least partiallycover the enclosure of the electronic device when the electronic deviceis positioned in the cavity, and a near-field wireless communicationantenna coupled to the shell and detectable by the electronic device. Inresponse to detecting the near-field wireless communication antenna, theelectronic device may be configured to switch from the first graphicaloutput to the second graphical output. The first graphical output mayinclude a first background image, and the second graphical output mayinclude a second background image different from the first backgroundimage.

The electronic device may be a mobile phone and the protective case mayhave an exterior surface having a color. The first graphical output mayinclude a group of application icons and have a first color scheme andthe second graphical output may include the application icons and have asecond color scheme. The second color scheme may be different from thefirst color scheme and may correspond to the color of the exteriorsurface of the protective case.

The enclosure may define a back exterior side of the electronic device,a front exterior side of the electronic device, and a peripheralexterior side of the electronic device, the peripheral exterior sideextending from the back exterior side to the front exterior side. Theshell may further define a window region configured to allow a user totouch the front exterior side of the electronic device when theelectronic device is positioned in the cavity, a back wall configured toat least partially cover the back exterior side of the electronicdevice, and a side wall configured to at least partially cover theperipheral exterior side.

The protective case may further include an input system that includes anactuation member configured to be actuated by a user and a passiveantenna. Subsequent to detecting the near-field wireless communicationantenna and in response to the actuation member being actuated by theuser, the passive antenna may become detectable by the electronicdevice. The electronic device may be configured to execute an operationin response to detecting the passive antenna. The passive antenna maynot be detectable by the electronic device when the actuation member isunactuated. The electronic device may further include a camera system,the second graphical output may correspond to an image-captureinterface, and actuation of the actuation member may cause theelectronic device to capture an image using the camera system.

A dock for an electronic device may include a support structureconfigured to position the electronic device in a viewable orientationwhen the dock is on a surface of an object, a near-field wirelesscommunication antenna configured to cause the electronic device todisplay a graphical user interface in response to the electronic devicebeing positioned on the support structure, and an input systemconfigured to wirelessly communicate with the electronic device inresponse to the input system being actuated by a user when theelectronic device is positioned on the support structure. The inputsystem may include an actuation member and a passive antenna, and, inresponse to the actuation member being actuated by the user, the inputsystem may wirelessly communicate with the electronic device using thepassive antenna.

The graphical user interface may be a secondary graphical userinterface, and the electronic device may be configured to switch fromdisplaying the secondary graphical user interface to displaying aprimary graphical user interface in response to being removed from thesupport structure.

The graphical user interface may correspond to an alarm clock functionof the electronic device, and actuation of the input system may causethe electronic device to change a setting of the alarm clock function.The dock may further include a speaker, the graphical user interface maycorrespond to an audio playback function of the electronic device, andactuation of the input system may cause the electronic device to changean operational parameter of the audio playback function. The dock mayfurther include a wireless charging system comprising an output coilconfigured to inductively couple to a charging coil of the electronicdevice when the electronic device is held by the support structure.

A handheld electronic device may include an enclosure, a display, atouch sensor positioned within the enclosure, and a near-field wirelesscommunication system configured to detect when the handheld electronicdevice is in proximity to any one of a set of docking accessories. Whenthe near-field wireless communication system detects that the handheldelectronic device is in proximity to a first docking accessory of theset of docking accessories, the handheld electronic device maytransition from a first mode of operation to a second mode of operationdifferent from the first mode of operation, and, when the near-fieldwireless communication system detects that the handheld electronicdevice is in proximity to a second docking accessory of the set ofdocking accessories, the handheld electronic device may transition fromthe first mode of operation to a third mode of operation different fromthe first mode of operation and from the second mode of operation.

The first docking accessory may be in a first location and the seconddocking accessory may be in a second location different from the firstlocation. Transitioning from the first mode of operation to the secondmode of operation may include transitioning from displaying a primarygraphical user interface comprising a set of application icons todisplaying a first auxiliary graphical user interface comprising a firstset of graphical objects that are relevant to the first location, andtransitioning from the first mode of operation to the third mode ofoperation may include transitioning from displaying the primarygraphical user interface to displaying a second auxiliary graphical userinterface different from the first auxiliary graphical user interfaceand comprising second set of graphical objects that are relevant to thesecond location.

Transitioning from the first mode of operation to the second mode ofoperation may include transitioning from displaying a primary graphicaluser interface to displaying a first auxiliary graphical user interface,and transitioning from the first mode of operation to the third mode ofoperation may include transitioning from displaying the primarygraphical user interface to displaying a second auxiliary graphical userinterface different from the first auxiliary graphical user interface.The first auxiliary graphical user interface may include a firstuser-defined set of graphical objects selected from a group of candidategraphical objects and the second auxiliary graphical user interface mayinclude a second user-defined set of graphical objects selected from thegroup of candidate graphical objects. The first user-defined set ofgraphical objects may include an audio control input object. The seconduser-defined set of graphical objects may lack the audio control inputobject. The first user-defined set of graphical objects may be arrangedon the display according to a user-defined arrangement.

A method according to some implementations is performed at a computersystem with a display, a housing, and an attachment mechanism. Thecomputer system detects attachment of an accessory to the computersystem, where the accessory, while attached, has a predeterminedorientation relative to the attachment mechanism. In response todetecting the attachment of the accessory to the computer system, and inaccordance with a determination that the accessory is a first accessorywith first physical dimensions, the computer system displays, on thedisplay, a first visual indication that the accessory has been attachedto the computer system, wherein the first visual indication indicates atleast one property of the first physical dimensions. In response todetecting the attachment of the accessory to the computer system, and inaccordance with a determination that the accessory is a second accessorywith second physical dimensions that are different from the firstphysical dimensions, the computer system displays, on the display asecond visual indication that the accessory has been attached to thecomputer system. The second visual indication indicates at least oneproperty of the second physical dimensions, and the second visualindication is different from the first visual indication.

A method according to some implementations is performed at a computersystem with a display and a housing. The computer system displays afirst graphical user interface comprising first graphical contentdisplayed in a first region of the display and second graphical contentdisplayed in a second region of the display, the second region differentthan the first region. The computer system detects a coupling of a caseto the computer system, where the first region of the display is coveredby the case and the second region of the display is visible through anopening in the case. In response to detecting the coupling of the caseto the computer system, the computer system transitions from displayingthe first graphical user interface to a second graphical user interface.The transition includes ceasing to display the second graphical contentin the second region of the display, and displaying the second graphicaluser interface on the display, the second graphical user interfacecomprising third graphical content, different from the second graphicalcontent, displayed in the second region of the display.

A method according to some implementations is performed at a computersystem with a display and a housing. The computer system detects anoccurrence of an event. In response to detecting the occurrence of theevent, and in accordance with a determination that a case is not coupledto the computer system, the computer system displays, in a first regionof the display, first graphical content associated with the event. Inresponse to detecting the occurrence of the event, and in accordancewith a determination that the case is coupled to the computer system,the computer system displays, in a second region of the displaydifferent than the first region of the display, second graphical contentassociated with the event. The first region of the display is covered bythe case when the case is coupled to the computer system, and the secondregion of the display is visible through an opening in the case when thecase is coupled to the computer system.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like structural elements, and in which:

FIG. 1A depicts an example system including an electronic device andassociated accessories;

FIG. 1B depicts the device of FIG. 1A and an example accessory in usetogether;

FIGS. 2A-2B depict an example wireless charging system for the device ofFIG. 1A;

FIG. 3A depicts several example protective cases for the device of FIG.1A;

FIGS. 3B-3C depict the device of FIG. 1A being used with an exampleprotective case;

FIGS. 3D-3F depict the device of FIG. 1A being used with another exampleprotective case;

FIGS. 3G-3I depict a device being used with an example removableaccessory;

FIGS. 3J-3L depict a device being used with another example removableaccessory;

FIGS. 3M-3N depict the device of FIG. 1A being used with another exampleprotective case;

FIGS. 3O-3P depict the device of FIG. 1A being used with another exampleremovable accessory;

FIG. 4 depicts several additional example devices holders for the deviceof FIG. 1A;

FIG. 5 depicts several additional example protective cases for thedevice of FIG. 1A;

FIG. 6 depicts an example group of candidate graphical objects forcreating user-defined auxiliary graphical user interfaces;

FIG. 7 depicts several example docks for the device of FIG. 1A;

FIG. 8 depicts an example system of electronic devices and accessories;

FIGS. 9A-9C depict an example electronic device in use with an exampleaccessory;

FIGS. 10A-10C depict another example electronic device in use with theexample accessory;

FIGS. 11A-11B depict example visual indications for display on a devicein use with an accessory;

FIG. 12 depicts an example animation for a visual indication;

FIG. 13A-13C depict an example electronic device in use with anaccessory;

FIGS. 14A-14B depict an example electronic device in use with a case;

FIGS. 15A-15B depict an example electronic device in use with a case andan accessory;

FIGS. 16A-16B depict an example electronic device in use with additionalaccessories;

FIGS. 17A-17B depict an example electronic device having an accessoryattached and detached;

FIGS. 18A-18B depict an example electronic device in different states inuse with an accessory;

FIG. 19A depicts an example electronic device in use with a case;

FIG. 19B depicts another example electronic device in use with anothercase;

FIGS. 20A-20B depict an example electronic device in different states inuse with a case;

FIGS. 21A-21B depict example display regions of example electronicdevices;

FIG. 22 depicts an example electronic device in use with a case;

FIG. 23 depicts example graphical user interfaces of a device in usewith a case;

FIG. 24 depicts an example graphical user interface for a wirelesspayment process;

FIG. 25 depicts another example graphical user interface for a wirelesspayment process;

FIG. 26 depicts another example graphical user interface for a wirelesspayment process;

FIG. 27 depicts an example graphical user interface for accepting anincoming call;

FIG. 28 depicts an example graphical user interface for a voice-baseddigital assistant operation;

FIGS. 29A-29B depict example interactions with a device to displaydifferent graphical content on an electronic device;

FIG. 30 depicts a technique for user-selection of graphical objects todisplay on an electronic device;

FIG. 31 depicts an electronic device in use with a case;

FIGS. 32A-32B depict an example electronic device displaying differentgraphical content based on whether the electronic device is being usedwith a case;

FIG. 33 is a flow chart of a method for use with a computer system;

FIG. 34 is a flow chart of another method for use with a computersystem;

FIG. 35 is a flow chart of another method for use with a computersystem; and

FIG. 36 depicts example components of an electronic device.

DETAILED DESCRIPTION

Reference will now be made in detail to representative embodimentsillustrated in the accompanying drawings. It should be understood thatthe following description is not intended to limit the embodiments toone preferred embodiment. To the contrary, it is intended to coveralternatives, modifications, and equivalents as can be included withinthe spirit and scope of the described embodiments as defined by theappended claims.

The embodiments herein are generally directed to a system of electronicdevices and electronic device accessories that use near-field wirelesscommunication techniques to dynamically modify or change how a deviceoperates. For example, various different accessories for electronicdevices may each include near-field wireless communication antennas thatallow the accessories to be detected and identified by the electronicdevice. Once a particular accessory is detected near the electronicdevice, the electronic device may change its mode of operation in amanner that is unique to that particular accessory or type of accessory.

Various different types of accessories may be configured to usenear-field wireless communication systems to affect the operationalmodes and/or characteristics of devices that are using thoseaccessories. For example, a protective case for a mobile phone may beconfigured to change the operational mode of the mobile phone in onemanner, while charging docks change the operational mode of the mobilephone in another manner, while an “alarm clock” docking accessorychanges the operational mode of the mobile phone in yet another manner.The change in operational mode may correspond to and/or be accompaniedwith a change in the graphical user interface or graphical output thatis displayed by the mobile phone. For example, when the mobile phone isplaced in a sport-focused protective case, the mobile phone may, withoutadditional user input, replace its primary graphical user interface (orany graphical user interface that is currently active) with asport-focused interface. As another example, when the mobile phone isplaced on a speaker dock, the mobile phone may replace its primarygraphical user interface with a set of audio playback controls. Thegraphical user interfaces that are activated when a device is used withan accessory may therefore be customized to a particular function or setof functions that are relevant to the associated accessory. In somecases, these graphical user interfaces may be simpler than a primarygraphical user interface (e.g., having fewer and/or larger graphicalobjects), which may help facilitate more efficient use of the device andmay be dedicated to a particular function set or operational mode of thedevice.

In some implementations described herein, one or more graphical outputsthat are displayed on the device are changed or switched in response todetecting the protective case. As used herein, graphical outputs may beused to refer to visible output from a display. Graphical outputs mayinclude graphical user interfaces, graphical objects, images, videos,and/or other visible outputs produced by a display. Graphical userinterfaces may include various types of graphical objects, includingicons, menu items, status bars, menus, graphical objects indicatinginformation such as wireless signal strength, time, battery chargelevel, and the like. Graphical user interfaces may also includegraphical outputs such as background images. Graphical objects may bevisually differentiable from other graphical objects, and the boundariesand/or borders of a graphical object may suggest functional distinctionsbetween different graphical objects. For example, the boundary and/orborder of a first icon (e.g., a first graphical object) may visuallydifferentiate the first icon from a second icon, and may indicate to auser that the two icons define different input areas and will, ifselected, cause a device to take different actions.

As used herein, the terms “switch” or “change” a graphical output may beused to refer to a scenario in which one graphical user interface,graphical object, or other displayed item is exchanged with anothergraphical user interface, graphical object, or other displayed item. Theterms “switch” or “change” may also be used to refer to a scenario inwhich a graphical user interface, graphical object, or other displayeditem is modified to produce a visually distinct or visually perceptibleeffect. For example, a background or color scheme of one or moregraphical objects in a graphical user interface may be “switched” or“changed” to appear to have a different color, texture, or othervisually perceptible feature. For clarity, the switched or changedgraphical output may be referred to as a second graphical output eventhough, other than an appearance, the graphical output may represent thesame item or perform the same function when selected.

For the purposes of this disclosure, accessories may include, withoutlimitation, protective cases, gaming cases, camera cases, and docks(e.g., speaker docks, alarm clock docks, charging docks, unpowereddocks, etc.). Cases, such as protective cases, gaming cases, cameracases, may be accessories that are configured to receive an otherwisecomplete device, such as a mobile phone, and may provide additionalfunctionality to the device (e.g., physical protection, appearance,attachment mechanisms, etc.). Such accessories that include near-fieldwireless communication antenna and cause an electronic device to changeor modify the operational mode and/or characteristic of the electronicdevice when the device and the accessory are in proximity to one anothermay be referred to herein as a near-field wireless enabled accessory.

The changing or modifying of the operational mode and/or characteristicsof electronic devices may be facilitated by near-field wirelesscommunications that allow the electronic devices to determine when theyare being used with the accessories. For example, the accessories mayinclude near-field wireless communication antennas, and the devices mayinclude near-field wireless communication systems that can detect whenthe device is in close proximity to the near-field wireless antennas(e.g., the device can detect when it has been installed in, coupled to,placed on, or is otherwise being used with the accessory). The devicemay also receive, from the near-field wireless communication antenna,information about the particular accessory such as a unique identifier.

The near-field wireless communication systems and antennas may beconfigured so that an accessory is detected by a device only when thedevice is sufficiently close that it is substantially certain that thedevice and the accessory are being used together. For example, in thecase of a protective case for a mobile phone, the mobile phone maydetect the presence of the case only once the phone is inserted into theprotective case. In the case of a docking accessory (also referred toherein as a “dock”), the mobile phone may detect the presence of thedocking accessory only once the mobile phone is physically placed on thedocking accessory. Further, the near-field wireless communicationantennas may be passive or un-powered antennas, allowing dynamic devicecustomization to occur even with un-powered accessories. As used herein,passive or un-powered antennas refer to antennas that are notconductively coupled to an electrical power supply of the accessory.Accordingly, a protective case need not have batteries or independentlypowered communications systems (e.g., WIFI or Bluetooth) in order tochange the operational mode or other characteristic of the electronicdevice. In some cases, however, devices may include both un-powerednear-field wireless communication antennas as well as poweredcommunications systems.

By providing a series of different accessories that can each customizethe operation or user interface of a mobile device in a different way,the mobile device may become an even more dynamic, useful tool. Forexample, throughout a day, a user may place a mobile device in a workoutcase for a morning workout, in a charging dock during work, in a kitchendock in the evening, and in an alarm clock dock at night. The conceptsdescribed herein allow the device to automatically transition to aworkout interface when it is placed in the workout case, to a workinterface when it is placed in the charging dock, to a cooking interfacewhen it is placed in the kitchen dock, and to an alarm clock interfacewhen it is placed in the alarm clock dock, among numerous other possibletransitions. The device may also transition back to a main or primaryinterface when it is removed from those docks (or in response to a userrequest regardless of its proximity to an accessory). In this way, thedevice continuously and automatically adapts to its intended use andprovides a tailored user interface to its user.

Further, the device may use other inputs and/or information to determinehow to change or modify its operations when the device is being usedwith a near-field enabled accessory. For example, when the devicedetects that it has been attached to a dock of an exercise bike, it mayalso determine the location of the device. If the location is a firstlocation (e.g., a home location), the device may take a different set ofactions than if the location is a second location (e.g., a fitnesscenter or gym). In the home location, the device may initialize a firstset of user controls, such as a set of media controls for the user'shome media system (e.g., the user's television, stereo equipment, etc.)and a fitness tracking interface, while in the fitness center, thedevice may initialize a second set of user controls, such as the fitnesstracking interface and a set of media controls for a personal streamingservice (e.g., to provide audio to the user's personal headphones). Asanother example, when the device detects that it has been placed on adock in a kitchen, the device may also determine who is using thedevice. If it is a first user, the device may display one set ofinterface elements (e.g., a recipe for a smoothie and an editablegrocery list), and if it is a second user, the device may display asecond set of interface elements (e.g., a recipe for a pasta sauce and aset of media controls for the user's home media system).

Information from any sensor and/or sensor system of a device may be usedto provide additional contextual information about the device, its use,its user, or the like, in order to provide highly customized andtailored user experiences. Such sensors and/or sensor systems mayinclude, without limitation, integrated cameras, GPS or other navigationor location-finding systems, thermal sensors, accelerometers,magnetometers, biometric identification systems (e.g., facialrecognition, fingerprint recognition, voice recognition), biometricsensors (e.g., heart-rate monitors, electrocardiographs, pulseoximeters), or the like. Other types of information not detected by anonboard sensor may also be used to provide additional contextualinformation about the device, its use, its user, or the like. Suchinformation includes, without limitation, current or predicted weatherinformation, date and time information, calendar entries, recentlyopened or closed applications, text or email messages, or the like. Suchinformation may be stored on the device, accessed via a communicationsnetwork, or the like. In some cases, devices use information about anaccessory (from a near-field wireless connection with the accessory)together with additional contextual information (e.g., from a sensorsystem or other information source) to determine how to change, modify,or affect the device's operation. For example, the device may determinewhich application to initiate based on the near-field wirelessconnection and a location of the device. Examples of using additionalcontextual information to determine how to change or affect theoperation of a device being used with a near-field wireless enabledaccessory are provided herein.

FIG. 1A depicts an example system in which an electronic device 100(also referred to herein simply as “device”) may be used with variousdifferent accessories that cause the device 100 to transition betweenoperating modes when the device 100 is used with those accessories. Theelectronic device 100 is an example of a computer system, such as thecomputer system described herein with respect to FIG. 36. As describedherein, transitioning between operating modes may include and/or beaccompanied by the initiation and/or termination of applications (e.g.,initiating or terminating an application in response to detectingaccessories), changes in the graphical user interface or graphicaloutput displayed by the device 100 (e.g., changes in the color, content,appearance, size, icons, or information of a graphical user interface),changes in device settings (e.g., alert volume, haptic or tactile outputstrength, screen brightness), or the like. Transitioning betweenoperating modes (or between different graphical user interfaces or othergraphical outputs) may or may not include or be accompanied by a visualanimation, sequence, or other graphical effect indicating or occurringduring the transition.

The device 100 shown in FIG. 1A is a mobile phone (e.g., a smartphone),but this is merely one representative example of a device that may beused in conjunction with the ideas disclosed herein. Other exampledevices include, without limitation, music/media players, tabletcomputers, laptop computers, wearable electronic devices, watches (e.g.,mechanical, electrical, or electromechanical), and the like.

The device 100 includes an enclosure 102 that defines the exteriorsurfaces of the device 100. The enclosure 102 may include, for example,a housing member 103 that defines a back exterior side of the device 100(e.g., back side 201, FIG. 2), a front exterior side of the device 100,and a peripheral exterior side 131 of the device 100, the peripheralexterior side extending from the back exterior side to the frontexterior side. The housing member 103 may be a single piece of material(e.g., a monolithic component), or multiple discrete components. Theenclosure 102 may also include a transparent cover 105 that covers orotherwise overlies a display 104 and/or a touch sensitive surface (e.g.,a touchscreen) of the device 100, and may define a front exterior frontsurface of the device 100. The display 104 is configured to displaygraphical outputs, and the graphical outputs may be visible through thetransparent cover 105 or at least a region of the transparent cover 105.The transparent cover 105 may also define one or more openings to allowinternal components such as microphones, cameras, speakers, sensors, andthe like, to have access to the surrounding environment of the device100. The device 100 may also include a touch sensor that is configuredto detect touch events or touch inputs applied to the transparent cover105. The touch sensor may be integrated with the display or otherwiseconfigured to provide touchscreen functionality.

The device 100 may include a near-field wireless communication system106 that is configured to wirelessly detect when the electronic deviceis in proximity to any one of a group of near-field wireless enabledaccessories. The near-field wireless communication system 106 may beconfigured for any suitable type or protocol of near-field wirelesscommunications, including but not limited to near-field communications(“NFC”) protocols, radio frequency identification (“RFID”) protocols, orany other suitable type or protocol. For example, the near-fieldwireless communication system 106 (and indeed any near-field wirelesscommunication system, antenna, or other component described herein) maybe configured to operate in accordance with applicable standards, suchas ISO/IEC 14443, FeliCa, ISO/IEC 18092, ISO/IEC 21481, ISO/IEC 13157,or the like.

In some cases, the near-field wireless communication system 106 isconfigured to detect the presence or proximity of passive or un-poweredantennas that are incorporated in the accessories. As such, thenear-field wireless communication system 106 may be separate from othercommunication systems in the device 100, such as Bluetooth, WIFI, orcellular communications systems, and may be configured to communicateover a limited range (e.g., the near-field wireless communication system106 may only detect a near-field wireless antenna when they are withinabout 10 cm from each other).

The device 100 may include physical inputs, such as a button 108, withwhich a user can interact to control operations of the device 100. Theparticular function of the button 108 may be changed based on theaccessory with which the device 100 is associated at a given time. Forexample, as described herein, in a primary operating mode, the button108 may serve to activate or deactivate the screen of the device 100. Ina second operating mode, such as when the device 100 is in a caseintended for capturing photographs, the button 108 may operate as ashutter button to capture an image. While the device 100 is shown havingone button 108, this is merely representative and the device 100 mayinclude more or different input mechanisms, including for exampleseparate volume control buttons, fingerprint sensors, rotatable inputmembers, keys, a keyboard, or the like. The device 100 may also includea wireless charging system, described with respect to FIG. 2.

The device 100 may also include various additional internal componentsand structures, such as sensor(s), memory, processor(s), controlcircuitry, a battery, circuit board (s), a frame or other supportingstructure, antenna(s), or the like. The device 100 may also includefront and/or rear facing camera systems (e.g., a rear-facing camera 214,FIG. 2) that can capture images and/or video of external subjects. Thecamera systems may include lenses, image sensors, focusing and zoomingmechanisms, flashes, and any other suitable components.

Additional or different components may also be positioned within theenclosure 102 of the device 100. The device 100 may also include varioussystems and/or components that can receive information from or about auser or the user's surroundings (e.g., touchscreens, microphones,biometric sensors, GPS systems). It is well understood that the use ofpersonally identifiable information (such as information from or about auser or the user's environment and that is stored on or accessible by adevice) should follow privacy policies and practices that are generallyrecognized as meeting or exceeding industry or governmental requirementsfor maintaining the privacy of users. In particular, personallyidentifiable information data should be managed and handled so as tominimize risks of unintentional or unauthorized access or use, and thenature of authorized use should be clearly indicated to users.

The system shown in FIG. 1A also includes various types of accessoriesthat can be used with the device 100. For example, FIG. 1A includesprotective cases 112, docks 114, a dock 116 with auxiliary input systems117, a speaker dock 118, and protective cases 120 with auxiliary inputsystems 121. As described herein, the device 100 may be useable witheach of these accessories (as well as others not shown in FIG. 1A), andas the user switches from one accessory to another, the device 100 maydynamically switch to a different operational mode, present a differentgraphical user interface or graphical output (e.g., present a graphicaluser interface having different content or a different appearance, coloror the like), change a device setting, or otherwise operate in a mannerthat is tailored to the particular accessory with which the device 100is being used. Docks, such as the docks 114, may include stand-aloneaccessories as well as docks that are integrated into other devices,such as exercise equipment (e.g., bicycles, rowing machines, ellipticalmachines, stair-climbing machines, or the like), vehicles, musicalequipment (e.g., guitars, amplifiers, keyboards, etc.), or the like. Thedocks 114 are shown with optional ledges 115 that support or prop thedevice 100 in a convenient viewing position. In some cases, the docks114 may lack the ledges 115, and the device 100 may be retained to thedock 114 and/or maintained in a particular orientation or position usingmagnetic attachment features in the dock 114 and the device 100.

Each accessory may include a near-field wireless communication antenna110 (also referred to herein simply as “antenna”) that is detectable bythe near-field wireless communication system 106 of the device 100. Asused herein, an antenna may be detectable insofar as the antenna ornear-field wireless communication circuitry is capable of producing anelectrical response when probed or polled by a wireless detection deviceor circuitry. For example, the antenna may produce a distinct orrecognizable disturbance or other response to an electromagnetic fieldproduced by another device or circuit, thereby rendering the antennadetectable. Further, as used herein, a near-field wireless communicationantenna being detectable indicates that the near-field wirelesscommunication antenna may be operable to trigger, initiate, or otherwisecause a response in a near-field wireless communication system of adevice, where the response indicates that the near-field wirelesscommunication antenna is in the presence and/or proximity of the device(e.g., within a threshold distance).

When the device 100 detects that it is being used with one of theaccessories in FIG. 1A, for example because it is within a shortdistance of an accessory (e.g., less than about 10 cm), the detectedantenna 110 causes the device 100 to change a mode of operation. As usedherein, changing a mode of operation may refer to or include changing agraphical output of the device (e.g., temporarily or permanentlychanging a color scheme of some or all of a graphical user interface,changing between different graphical user interfaces, initiating thedisplay of graphical objects), changing one or more device settings, orcombinations of these. To facilitate this functionality, each antenna110 may include some identifier or other information that uniquelyidentifies that accessory (or that type of accessory) or may otherwisebe configured to uniquely modify the operation of the device 100. Inthis way, the operation of the device 100 may dynamically change as auser changes from accessory to accessory.

The antennas 110 may be any suitable type of antenna that is detectableby the near-field wireless communication system 106 of the device 100.For example, the antennas 110 may be NFC antennas, RFID antennas, or thelike. In some cases, the antennas 110 may be passive or un-poweredantennas. Accordingly, the accessories need not be powered or includebatteries or other power sources to cause the device 100 to change itsoperational mode. This may allow accessories to be smaller, thinner,lighter, and more portable than they would be if they required powersources. In some cases, an antenna 110 may be powered by a power sourceinternal to or otherwise connected to an accessory. Also, accessoriesthat use power for other purposes (e.g., speakers, amplifiers, etc.) mayuse passive or un-powered antennas despite the availability of power atthe accessory.

The near-field wireless communication antennas 110 may be positioned inthe accessories so that they are aligned with or otherwise suitablylocated so that they can be detected by the near-field wirelesscommunication system 106 when the device 100 is being used with theaccessory. Thus, for example, when the device 100 is installed in aprotective case 112, the near-field wireless communication antenna 110of that case may be substantially aligned with the near-field wirelesscommunication system 106 of the device 100 (e.g., within about 2 cm, orabout 1 cm). The antenna and near-field wireless communication system106 may be similarly aligned when the device 100 is placed on a dock114, 116, or 118.

As described, the device 100 may dynamically change its operational modewhen it is used with different accessories. In some cases, changingoperational modes includes changing between different graphical userinterfaces. FIG. 1B depicts the device 100 displaying a primarygraphical user interface 128 when the device 100 is not being used withan accessory (when it is being used with an accessory that causes thedevice 100 to display the primary graphical user interface 128), anddisplaying a different graphical user interface 130 when the device 100is being used with an accessory 129 (shown in this example as a dock).

The primary graphical user interface 128 may include selectable icons(e.g., application icons that, when selected, cause applications to beexecuted and/or initialized, or otherwise cause graphical userinterfaces associated with the applications to be displayed) or othergraphical objects that correspond to applications or other functions ofthe device 100. The primary graphical user interface 128 may alsoinclude status bars, menus, graphical objects indicating informationsuch as wireless signal strength, time, battery charge level, and thelike. The primary graphical user interface 128 may be automaticallydisplayed when the device 100 is turned on, and may be considered thetop level graphical user interface of the device 100 (or the highesthierarchical level of a multi-level graphical user interface scheme).The primary graphical user interface 128 may also be referred to as a“home screen,” and may be a main starting interface for an operatingsystem of a device. The primary graphical user interface 128 may alsohave a color scheme, which may refer to the color or colors ofbackground images, borders, screen areas, icons, or the like. As usedherein, a secondary graphical user interface may refer to any graphicaluser interface other than the primary graphical user interface.

When the device 100 is placed on an accessory and is positioned by theaccessory so that the device 100 can be seen and interacted with, thedevice 100 may change from the primary graphical user interface 128 toanother graphical user interface. For example, as shown in FIG. 1B, whenthe device 100 is placed on an accessory 129, the device 100 may changefrom the primary graphical user interface 128 to a second graphical userinterface 130 that is different than the primary graphical userinterface 128. The second graphical user interface 130 is merely one ofnumerous possible examples of graphical user interfaces that aredifferent from the primary graphical user interface 128 and to which thedevice 100 may switch in response to the device 100 being used with anaccessory. The change from the primary to the second graphical userinterface may be triggered by the device 100 detecting the near-fieldwireless communication antenna in the accessory 129.

The second graphical user interface 130 may have a different set oficons, inputs, outputs, or other types of graphical objects as comparedto the primary graphical user interface 128. For example, the secondgraphical user interface 130 lacks the application icons of the primarygraphical user interface 128, and instead includes other graphicalobjects, such as graphical objects 132 and 134. The graphical object 132may be a “world clock” graphical object (e.g., displaying the times ofmultiple time zones), and the graphical object 134 may be an “audiocontrol” graphical object (e.g., displaying now-playing information andincluding audio control affordances such as play, pause, skip forward,skip backwards, etc.). Accordingly, the second graphical user interface130 includes different graphical content and provides different devicefunctions than the primary graphical user interface 128. The device 100may automatically change back from the second graphical user interface130 to the primary graphical user interface 128 when the device 100 isremoved from the dock 129, or in response to a user input received whilethe device 100 is on the dock 129.

FIGS. 2A-2B illustrate a wireless charging system for the device 100.FIG. 2A, for example, shows a back view of the device 100 and a chargingdock 200 that is configured to wirelessly charge the device 100 when thedevice 100 is placed on the charging dock 200. FIG. 2B illustrates thedevice 100 positioned on the charging dock 200 in a chargingconfiguration (e.g., with the back surface of the device 100 resting onthe upper surface of the dock 200).

The device 100 includes a charging coil 206 within the device 100 andconfigured to inductively couple to an output coil 210 of the chargingdock 200 to charge the device 100. More particularly, the output coil210 of the charging dock may produce an electromagnetic field, which inturn induces a current in the charging coil 206 of the electronicdevice, and the induced current may be used to recharge the device'sbattery.

The device 100 may include a set of magnetic attachment features, suchas magnets 202, that are configured to facilitate alignment andretention of the device 100 to the charging dock 200. The charging dock200 may include a set of complementary magnets (or ferromagneticmaterials) 204 that are attracted to the magnets 202 to furtherfacilitate alignment and retention of the device 100 to the chargingdock 200. For example, the magnets 202 and complementary magnets (orferromagnetic materials) 204 may be configured so that when the device100 is brought into close proximity of the dock 200 by a user (e.g.,within 2 cm, 1 cm, or another suitable range), the magnets 202 andcomplementary magnets 204 pull the device 100 towards the dock 200 andinto a position that aligns the output coil 210 of the dock 200 with thecharging coil 206 of the device 100. The magnetic attraction may alsoprovide a retention force to hold the device 100 in the aligned positionand prevent the device 100 from slipping off the dock 200 duringcharging. While FIG. 2A describes the device as including magnets 202and the dock 200 as including magnets or magnetic materials 204, it willbe understood that any materials or combinations of materials that aremagnetically attracted to one another may be used in either the device100 or the dock 200. Further, the magnets and/or magnetic materials maybe arranged so that the device 100 magnetically couples to the dock 200in only one orientation. This may further help prevent misalignment andhelps ensure that the wireless charging function can operateefficiently. In some cases, other techniques for aligning the device 100with the dock 200 may be used instead or in addition to the magnets,such as alignment pins and recesses, clips, complementary shapedsurfaces, or the like.

In some cases, the dock 200 may include a near-field wirelesscommunication antenna, similar to the antennas 110 described withrespect to FIG. 1A. In this way, the device 100 can detect when it hasbeen placed on or is otherwise being held by the dock 200 using the samenear-field wireless communication system that it uses to detect thepresence of other accessories. (In other cases, the device 100 cancommunicate with the dock 200 using the charging and output coils or viaanother wireless protocol or technique.) When the device 100 detectsthat it is positioned on the dock 200 via the near-field wirelesscommunication system, it may change its mode of operation in a way thatis tailored to the dock 200. For example, as shown in FIG. 2A, thedevice 100 may display a graphical object 211 on the display 104. Thegraphical object 211 may be an overlay over a blank screen or over aprimary graphical user interface of the device 100. The graphical objectmay include inputs and outputs that are contextually related to the dock200 and/or the charging operation provided by the dock 200. For example,as shown the graphical object 211 displays a name or description of thedock 200 (e.g., “Bedroom Charger”), as well as inputs 212 that maycontrol one or more aspects of the charging operation. For example, theinputs 212 may allow the user to select different charging modes ordifferent power consumption modes of the device 100.

Other inputs and outputs may also be included instead of or in additionto those shown in FIG. 2B. For example, the graphical object may includeinputs and outputs that are relevant to a room where the dock 200 islocated. As used herein, a graphical object or graphical user interfacemay be considered relevant to a location, room, accessory, or the like,if the graphical object or graphical user interface provides access tofunctions or information that are germane to a context of the location.Thus, for example, if the dock 200 is in a bedroom, the graphical objectmay include an input for activating or deactivating an alarm. If thedock 200 is in a living room, the graphical object may include an inputfor controlling audio playback of the device 100 or a connected audiosystem (e.g., a home stereo or other device). If the dock 200 is in akitchen, the graphical object may include a recipe interface and one ormore timers. If the dock 200 is in a music room, the graphical objectmay include audio controls and a musical notation interface. In someimplementations, an association of an accessory (e.g., a dock) with aparticular room is based on an assignment of the accessory to a virtualroom in a smart home platform. A smart home platform may includenumerous virtual rooms or environments, and devices and/or smartaccessories may be associated with particular ones of the rooms and/orenvironments. For example, devices such as a television, audio system,and wirelessly-controllable lights may be assigned to a “living room”environment. In some implementations, a dock (e.g., the dock 200) isalso associated with or assigned to the “living room” environment in thesmart home platform. Accordingly, in some implementations, in responseto being placed on the dock in the living room, the device detects thatthe dock is associated with the “living room” environment, and displaysgraphical objects that are configured to control the devices assigned tothe “living room” environment (e.g., the television, audio system, andlights that are in the living room).

While FIGS. 2A-2B show a wireless charging system incorporated in adedicated charging dock, wireless charging systems analogous to thosedescribed with respect to FIGS. 2A-2B may be incorporated into the otheraccessories described herein. For example, a protective case may includea supplemental battery and an output coil to charge the device 100 whenthe device 100 is inserted into the case. Similarly, an output coil andalignment magnets may be incorporated into a speaker dock or alarm clockdock to allow the device 100 to charge when the device 100 is positionedon the dock. Also, wireless charging systems may be incorporated into astand-alone battery accessory that is configured to attach to the deviceand wirelessly charge the device from the battery. An example batteryaccessory is described herein with respect to FIGS. 3J-3L.

As described above, a device 100 may use a near-field wirelesscommunication system to detect that it is being used with an accessory,and to identify that particular accessory. Further, because near-fieldwireless communication antennas do not need to be powered in order tocommunicate with or be detectable by the near-field wirelesscommunication system of a device, even simple accessories such asprotective cases and simple device stands can trigger the device tochange its mode of operation or otherwise modify its behavior. FIG. 3Aillustrates several examples of protective cases for a device, such asthe device 100. The protective cases shown in FIG. 3A may be embodimentsof the protective cases 112 in FIG. 1A. Each protective case in FIG. 3Amay include a near-field wireless communication antenna 110, but maylack other circuits or components that interact with the device 100.Thus, even a simple protective case that appears to be nothing more thana single-piece of plastic or rubber may cause the device 100 to changeits operation in a different or unique way.

With reference to FIG. 1A, the protective cases in FIG. 3A may eachinclude a shell 124 that defines a cavity 125 in which the device 100may be positioned. The shell 124 may be configured to at least partiallycover the enclosure of the device 100 when the device 100 is positionedin the cavity 125. The shell 124 may further define a back wall 122 thatis configured to at least partially cover the back exterior side of theelectronic device (e.g., side 201, FIG. 2A) and a side wall 127configured to at least partially cover the peripheral exterior side 131of the device 100. The shell 124 may also define a window region 126configured to allow a user to touch the front exterior side of theelectronic device (e.g., the transparent cover 105) when the device 100is positioned in the cavity 125. The window region 126 may be an openarea such that the protective case covers all or substantially all ofthe back and side surfaces of the device 100, but leaves the transparentcover 105 substantially uncovered (e.g., such that more than 50%, 60%,70%, 80%, 90%, 95%, or 99% of the front surface of the transparent cover105 is uncovered).

The walls of the shell 124 (e.g., the back wall 122 and the side wall127) may be relatively thin. For example, in some cases, each of thewalls of the shell 124 have a thickness less than about 4 mm, about 3mm, about 2 mm, about 1.5 mm, about 1 mm, or any other suitabledimension. The shell 124 may increase the overall size of the device(e.g., the combined size of the shell with the device installed) by asmall enough amount that the primary functionality of the device 100 isnot fundamentally altered as a result of installing the device 100 inthe protective case. For example, if the device 100 is a mobile phonethat may be held and operated by a user's hand (e.g., a single hand),the device 100 the same or substantially the same use and/or handlingcharacteristics may be preserved when the device 100 is in theprotective case (e.g., it can still be held and operated by one hand).If the device 100 is a tablet that may be held and operated by one ortwo hands, it may be held and operated in the same or similar way evenwhen it is inserted in the protective case.

Each protective case in FIG. 3A may also include a near-field wirelesscommunication antenna 110 coupled to its shell and configured to causethe device 100 to switch from displaying the first graphical userinterface (or graphical output) to displaying a different graphical userinterface (or graphical output) in response to the electronic devicebeing positioned in the cavity. FIG. 3A shows how various differentexamples of protective cases may switch the graphical user interface ofthe device 100. For example, the device 100 in FIG. 3A that is not in aprotective case is shown displaying a first graphical user interface310. The first graphical user interface 310 may be a default or primarygraphical user interface, such as the primary graphical user interface128, FIG. 1B. In some cases, this graphical user interface 310 maydisplay selectable icons (e.g., application icons that, when selected,cause applications to be executed and/or initialized, or otherwise causegraphical user interfaces associated with the applications to bedisplayed) or other graphical objects that correspond to applications orother functions of the device 100. The first graphical user interface310 may also have a background image 311. The background image 311 mayalso be referred to as a wallpaper, and may be an image that isgraphically behind the application icons of the graphical userinterface. In some cases, the first graphical user interface 310 may actprimarily as an application selection screen. (The device 100 may alsohave a “lock screen” or “wake screen” that is displayed when the displayis active but the device 100 is locked. The lock screen may also have abackground image, which may also be referred to as a wallpaper.

The case 300 may be configured to cause the device 100 to ceasedisplaying a first graphical output (e.g., the first graphical userinterface 310) and instead display a second graphical output 312 that isdifferent than the first graphical output. As used herein, a secondgraphical user interface or graphical output may refer to any graphicaluser interface or graphical output that is different from the firstgraphical user interface or graphical output.

When the device 100 is placed in the case 300, the near-field wirelesscommunication system 106 of the device 100 detects the near-fieldwireless communication antenna of the case 300 in close proximity to thedevice 100 (e.g., within about 10 cm, 5 cm, 2 cm, or the like), andreceives information from or about the case 300 from the antenna. Theantenna may communicate an executable command to the device 100, or itmay communicate data that the device uses to select or lookup a commandor routine or otherwise determine how to change its operation.

The graphical output 312 that is initiated by the case 300 may includethe same application icons and provide the same functions as the firstgraphical user interface 310, but have a different background image 313.Thus, when the user installs the device 100 into the case 300, thedevice 100 may automatically transition to a different background image.In some cases, the different background image 313 is a modified versionof the background image 311. For example, a hue, saturation, colorbalance, or other image property of the background image 311 may bemodified to produce the different background image 313.

The different background image 313 may relate in some way to the case300. For example, if the case 300 is blue, the background image 313 maybe blue, or if the case 300 has a rainbow decoration on it, thebackground image 313 may be a rainbow. Accordingly, the graphical userinterface 310 may change or morph to graphically match or coordinatewith the case 300. In this way, a user can switch between cases havingdifferent colors, designs, appearances, or the like, and the appearanceof the graphical output of the device 100 will automatically changebased on the case to which it is coupled.

In addition to or instead of changing the background image, the device100 may display a second graphical output that includes the same iconsand background image as a primary graphical user interface, but has adifferent color scheme. A color scheme for a graphical user interfacemay include particular colors for backgrounds, application icons, statusbars, informational icons, and the like. The color scheme of the secondgraphical output may match or otherwise correspond to a color of anexterior surface of accessory (e.g., the case 300) in which the device100 is installed. For example, if the accessory is yellow, the secondgraphical output may include graphical elements that have the same orsimilar yellow color as the case. Notably, these elements may have adifferent color when the device 100 is not installed in the case. Insome cases, at least one graphical element of the second graphicaloutput has the same color as the accessory.

Other changes to the graphical user interface 310 (or other graphicaloutputs displayed by the device 100) are also contemplated. For example,instead of or in addition to switching to a different background image,the device 100 may change the arrangement of its icons, or the contentor appearance of a lock screen, change an overall color scheme of thegraphical user interface and/or background image, or the like.

Another case, such as the case 302, may have an antenna that causes thedevice 100 to transition from the first graphical user interface 310 toyet another graphical user interface 314 (e.g., a second graphical userinterface). The graphical user interface 314 may be a restrictedenvironment that reduces or otherwise changes the number or type ofavailable application icons, optionally changes the size of the icons,and locks the interface so that a user cannot leave the restrictedenvironment without a password or other type of authentication. Inaddition to changing the graphical user interface, other aspects of thedevice operation may be modified or changed. For example, notifications(e.g., ringer sounds, message previews, etc.) may be turned off orchanged to a different mode (e.g., where message content previews arenot displayed). As another example, access to media stored on the device100 may be restricted or limited, such as restricting movies or songsbased on a rating. In this way, the case 302 may be especially suitedfor use when the device 100 is being given to a child or friend fortemporary use, where the owner of the device 100 may wish to limitaccess to certain applications or functions.

Where the case 302 acts as a child-focused case, the case 302 itself mayinclude physical features that may be useful for a device being used bya child. For example, the case 302 may have extra padding or otherprotection to prevent damage during falls, sealing to prevent damagefrom spills, clear screen covers to prevent damage to or soiling of atransparent cover, grips or other features to facilitate being held bysmaller hands, or the like.

Another example case 304 may have an antenna that causes the device 100to display a graphical user interface or other graphical object that iscoordinated with a physical feature in the case itself, such as anopening in the case. For example, the case 304 includes a front cover316 that a user can open or close over the front of the device 100. Thefront cover 316 may include a window 318 that allows a portion of thedisplay of the device 100 to be viewed when the front cover 316 isclosed. When the device 100 detects that it is being used with the case304 and that the front cover 316 is closed, it may transition from thefirst user interface 310 to another graphical user interface 320 thatincludes a graphical object 322 that is positioned so that the graphicalobject 322 is aligned with and/or visible through the window 318. Thegraphical object 322 as shown includes the current time and weather,though any other information or image may be included instead of or inaddition to that shown. Further, the graphical object 322 may be remaindisplayed even when the front cover 316 is closed and after the displayof the device 100 would otherwise have turned off (e.g., to save power).The device 100 may detect that the front cover 316 of the case 304 isclosed using any suitable technique. For example, the device 100 maydetect that the front cover 316 is closed by detecting that afront-facing camera has been occluded, using a second near-fieldwireless communication antenna in the front cover 316, or any othersuitable technique.

Because the case 304 has a front cover 316, the device 100 may be moreoccluded or covered when it is in the case 304 than it would be inother, open-front cases (e.g., the case 300). Accordingly, when thedevice 100 detects that it is inside the case 304, it may change othersettings or functions of the device as well. For example, it mayincrease an alert volume to account for the muffling or volumeattenuation of the case 304. As another example, the device 100 maydecrease an alert volume or turn off alerts entirely, as the user mayuse the case 304 when they intentionally want to silence the device 100.The device 100 may also change how it provides graphical or visualnotifications, such as by displaying them in the area of the window 318so that they are visible when the front cover 316 is closed. Indeed, aswith any other accessory described herein, the user may customize howthe device 100 changes in operation when it is used with an accessory.For example, the user may select what graphical user interface shouldreplace the primary user interface (e.g., an array of applicationicons), what devices settings should change, and the like. While thecase 304 is shown as having a front cover that can open and close, othertypes of cases may have windows and operate in a manner similar to thecase 304 (e.g., a sleeve-type case with a window on one side of thesleeve).

Another example case 306 may be designed to hold the device 100 duringexercise or other physical activity. The case 306, for example, includesa strap 326 for attaching the case 306 and device 100 to a user (e.g.,to the user's arm or wrist). When the device 100 detects that it hasbeen inserted into the case 306 (e.g., when the device 100 detects thatit is close proximity to the antenna of the case 306), the device 100may transition to a graphical user interface 324 that is tailored foruse during exercise. For example, because devices such as smartphonesare often used as audio players during exercise, the graphical userinterface 324 may include large audio control buttons that are easy tosee and press even during exercise (e.g., buttons that are responsive totouch inputs in an area about one square inch or greater). The device100 may also suggest music or audio (e.g., a workout playlist) inresponse to detecting the case 306. The device 100 may also change adevice setting to accept or respond to different types of inputs than itdoes in a normal operating mode. For example, the device 100 may beconfigured to skip a song when a user knocks on or bumps the device 100,and change a volume of an audio output when the user swipes the palm oftheir hand up or down along the front surface of the device. The device100 may change its settings to respond to other types of inputs as well.

While FIG. 3A illustrates four example cases that may trigger devicechanges using a near-field wireless communication antenna, other typesof cases may also be provided. For example, a case for use when camping,hiking, or other outdoor activities may be configured to cause thedevice 100 to enter a power-saving mode or change device settings tohelp conserve power (e.g., reducing screen brightness, turning offcellular radios and WIFI radios, or the like). Such a case may alsoreplace a conventional lock screen or the primary graphical userinterface with a set of icons for features or applications that arerelevant to outdoor activities. For example, the device 100 may displaylarge buttons to activate a flashlight function, a compass function, amap or positioning application, and a weather application. As notedabove, the particular buttons that are displayed may be selected by auser based on his or her preferences when using that particular case.

As another example, a rugged case may be provided for when the device100 is being used in work environments or during outdoor activities suchas hiking, camping, fishing, boating, skiing, rock climbing, or thelike. Such a case may be ruggedized or otherwise be configured toprovide a greater degree of physical protection to the device, and maybe configured to cause the device 100 to replace a conventional lockscreen or the primary graphical user interface with a set of icons forfeatures or applications that are relevant to a particular activity orwork environment. For example, the device 100 may display buttons toactivate a flashlight function, a level function, a camera application,and a walkie-talkie function. As noted above, the particular buttonsthat are displayed may be selected by a user based on his or herpreferences when using that particular case.

As another example, a case may cause the device to change a backgroundimage or wallpaper to match or coordinate with a separate object. Forexample, a case may change a background image or wallpaper to match orcoordinate with the fabric of a handbag, backpack, purse, or otherobject that the device and case are being used with. If the case isintended to be used when the device is being carried in a bag, backpack,or purse, the case may also cause the device to increase a ringer volumeand/or a tactile notification amplitude to help a user hear or feeldevice notifications through the bag.

FIGS. 3B-3C illustrate an example of the device 100 being used with anaccessory case 330, in which the device 100 displays, on its display104, a color effect in response to being placed in a cavity 331 of aprotective case 330. In particular, as described herein, the device 100detects, with its near-field wireless communication system, that it isin close proximity to the case 330, and receives information about thecase to determine what color effect to display.

FIG. 3C depicts an example color effect 333 that may be produced inresponse to the device 100 detecting that it is being used with the case330. The color effect depicted in FIG. 3C may appear as a wash of colorthat sweeps across the display 104. The color effect 333 may be anyvisible change in a characteristic of the graphical output of thedisplay 104. For example, if the display 104 is displaying a backgroundimage, the color effect 333 may be a change in the hue, tint, shade,tone, saturation, etc., of the background image. The color effect mayalso be an image, pattern, or the like. The color effect 333 may have avisual relevance to the color or use of the protective case 330. Forexample, the color effect 333 may match or be similar to the color ofthe case 330. As another example, the color effect 333 may have acontextual relevance to the use of the case, such as a ruggedized casefor outdoor use causing the color effect 333 to have a camouflageappearance.

Returning to FIG. 3C, at time t₀, the color effect 333 may appear on thedisplay 104. At time t₁, the color effect 333 (a border of the colorchange) has moved a distance across the display 104, and at time t₂, thecolor effect 333 has moved fully across the display 104. This may be theend of the color effect 333 (e.g., the color change persists until thedevice 100 is removed from the case or another event occurs), or thecolor effect 333 may continue with additional changes. For example, the“wash” of color may fade away or continue to move across the display 104until it is gone and the original, unaltered graphical output (e.g.,before time t₀) is once again displayed by the display 104. In caseswhere the color effect 333 (e.g., the change of color of the graphicaloutput) persists until the device 100 is removed from the case 330, thecolor effect animation shown in FIG. 3C may be reversed in order toreturn the graphical output to the original, unaltered color (e.g., thecolor effect may animate from t₂ to t₀, instead of from t₀ to t₂).

The color effect 333 shown in FIG. 3C may be displayed while othergraphical objects or graphical user interfaces are being displayed bythe display 104. For example, the display 104 may display iconsassociated with a main or primary user interface of an operating systemof the device. The icons may appear to be in front of (or on top of) abackground image. The color effect 333 may affect any portion or segmentof the graphical output on the display 104. For example, the coloreffect 333 may result in visual changes to both the background image andthe icons of a graphical user interface, or it may result in visualchanges to the background image but not the icons of a graphical userinterface, or to the icons but not the background image. The coloreffect 333 may also be displayed in conjunction with user interfacesother than the main or primary user interface. For example, the coloreffect 333 may be displayed while a graphical user interface of anapplication (e.g., a program that is executed by or on the operatingsystem) is being displayed.

The graphical user output that is displayed when the color effect 333 isnot present may be considered a different graphical output than thatwhich is displayed when the color effect 333 is present. Stated anotherway, when the color effect 333 is not present, the device may beconsidered to be displaying a first graphical output, and when the coloreffect 333 is present (even transiently), the device may be consideredto be displaying a second graphical output. These are merely examples ofthe ways in which a color effect 333 may affect the appearance of thegraphical outputs on the display 104, and others are also contemplated.

FIG. 3D illustrates an example of the device 100 being used with anaccessory case 334, in which the device 100 displays a graphical outputthat is coordinated with a physical feature in the case 334 itself, suchas an opening in the case. For example, similar to the case 304, thecase 334 defines a window 336 that allows a portion of the display 104of the device 100 to be viewed when the device 100 is in the case 334.When the device 100 detects that it is being used with the case 334(e.g., using the near-field wireless techniques described herein), thedevice 100 may transition from displaying a first graphical output 337(which may be main or primary graphical user interface, a graphical userinterface of an application, or the like) to displaying anothergraphical output, such as a graphical object that is aligned with and/orvisible through the window 336.

The case 334 may define an opening 335 along a side of the case 334 toallow the device 100 to be slid into the case 334. The opening 335 maybe the only opening that is configured to allow the device to be putinto the case 334. While the opening 335 is shown on the side of thecase 334 that has the smallest area, the opening 335 may be along adifferent side of the case 334 in other implementations (e.g., a longside 377) of the case 334.

FIG. 3E illustrates the device 100 inserted into the case 334. Once thedevice 100 detects that it has been inserted into the case 334 or isotherwise being used with the case 334, (e.g., with near-field wirelesstechniques), the device 100 transitions from displaying the firstgraphical output 337 (e.g., a primary graphical user interface) todisplaying a second graphical output 344. The second graphical output344 is different than the first graphical output 337, and, as shown,includes a graphical object having a size, shape, and position on thedisplay 104 that coordinates with the window 336. Notably, the graphicalobject of the second graphical output 344 may appear out-of-place or mayimpede the display of the main graphical user interface if the device100 were not in the case 334. The second graphical output 344 as shownincludes the current time 376, a message notification icon 338, and acall notification icon 339, though any other types of icons orinformation may be included. The message and call notification icons mayalso include a number of unread or recent messages or calls, thusenabling a user to quickly access information that might be useful tosee without having to remove the device 100 from the case 334.

FIG. 3F illustrates the device 100 inserted into the case 334, with thedevice 100 displaying a third graphical output 345. The third graphicaloutput 345 may include a graphical object that is used in place of thesecond graphical output 344. The particular content, arrangement,appearance, or other property of the graphical object(s) displayed inthe window 336 may be user selectable or configurable. For example, auser of the device 100 may select whether the second or third graphicaloutput 344, 345 is displayed when the device 100 is inserted into thecase 334. The third graphical output 345 may include the current time340, a weather indicator 393 (which may display a graphical depiction ofthe current weather), a day/date indicator 342, and a notificationindicator. The notification indicator may signal that a new notificationis available for the user. The notification may indicate, for example,that an event has occurred on the device 100 (e.g., a voice message hasbeen received, an incoming call was missed, an application has issued anotification or message, a text or email message has been received,etc.). The content of the third graphical output 345 may be configuredto convey information more succinctly and efficiently than aconventional graphical user interface. For example, instead ofindicators that differentiate between different types and amounts ofrecently received messages, the graphical output 345 includes thenotification indicator 341 that relates to multiple different kinds ofmessages. This type of streamlined graphical output may improve thefunctionality of the device 100 by allowing the user to interact withthe device in different ways under different circumstances or use cases.For example, instead of requiring a user to remove the device 100 tocheck for messages or to see the time, the user can simply glance at thedevice 100 through the window 336 to see the desired information.Further, while the same information may also be displayed in a main orprimary user interface, the main or primary interface may show theinformation in smaller or less easily-viewable forms. As such,displaying the information in a more efficient, readable form improvesthe overall usability of the device and the usefulness of the device 100when it is in the case 334.

As noted above, various types of accessories may be configured to usenear-field wireless communication systems to affect the operationalmodes and/or characteristics of devices that are using thoseaccessories. FIGS. 3A-3F, for example, illustrate examples where theaccessory is a protective case for a device. Another type of accessorymay be configured to mount to the device and/or a protective case of thedevice (e.g., on a back surface of the device or case). FIGS. 3G-3Iillustrate one such example accessory.

FIG. 3G depicts a device 346 (which may be in a protective case) and acard wallet accessory 347 that is configured to be removably attached toa surface 351 (e.g., a back surface) of the device 346. The device 346may be or may be an embodiment of the device 100, and may be the same asor similar to the device 100.

The card wallet accessory 347 may include a near-field wirelesscommunication antenna 348 that is detectable by the near-field wirelesscommunication system of the device 346. The card wallet accessory 347may define a first opening 358 that is configured to allow an object(e.g., a bank card 350) to be placed into and removed from an internalcavity of the card wallet accessory 347. The card wallet accessory 347may also define a second opening 349, which may allow the contents ofthe card wallet accessory 347 to be visible to a user and may also allowthe user to touch the contents of the card wallet accessory 347 in orderto slide the contents out of the card wallet accessory 347. The cardwallet accessory 347 may also include magnetic attachment features 359that are configured to removably attach the card wallet accessory 347 tothe device 346 via complementary magnetic attachment features 360 of thedevice 346. The magnetic attachment features 359, 360 may includemagnets, ferromagnetic materials, or the like. In some cases, the device346 may include a metal plate or sheet so that the card wallet accessory347 may be positioned anywhere along the surface 351.

FIG. 3H shows the card wallet accessory 347 removably attached to thesurface 351 of the device 346. As described for other near-fieldwireless enabled accessories, in response to detecting that the cardwallet accessory 347 has been attached to the device 346, the device 346may take an action or change a mode of operation. In the case ofattaching the card wallet accessory 347, the device 346 may log alocation of the device when the card wallet accessory 347 was attached,or display a graphical object (e.g., a notification object that overliesa portion of a graphical user interface) acknowledging that the cardwallet accessory 347 has been attached. In some cases, instead of or inaddition to detecting the card wallet accessory 347, the device 346 maydetect the contents of the card wallet accessory 347. For example, abank card may include a near-field wireless communications antenna thatthe device 346 can detect. In such cases, in response to detecting thatthe card wallet accessory 347 has been attached, the device 346 maydetermine the identify of any near-field wireless enabled cards in thecard wallet accessory 347 and provide an indication to the user of thecontents. As a particular example, a name, icon, or other indicator ofeach card in the card wallet accessory 347 may be displayed on thedevice's display so that a user can easily see what cards are availablejust by viewing the display.

In the case where the device 346 can detect the presence or proximity ofcards or other objects in the card wallet accessory 347, it can alsotake certain actions in response to detecting that a card has beenremoved from the card wallet accessory 347. FIG. 31 illustrates anexample in which a bank card 350 has been removed from the card walletaccessory 347. In response to detecting the removal, the device 346displays one or more graphical objects that are relevant or related tothe removed card 350. For example, the device 346 may display a firstgraphical object 352, which may be an image of the particular bank card350 that was removed. The device 346 may also display a second graphicalobject 353, which may be a recent purchase history associated with thebank card 350. Other types of information and/or graphical objects maybe displayed instead of or in addition to those shown in FIG. 3I.

In other cases, the device 346 may take other actions, initiate otherapplications, or display other types of graphical objects in response todetecting that a card (or the card wallet accessory 347) has beenremoved from the device 346. For example, the device 346 may launch awallet application or a finance application. As another example, thedevice 346 may open an application based on the location of the device346 when the card is removed. More particularly, because the removal ofthe bank card 350 may indicate that the user is about to make apurchase, the device 346 may determine if its location at that timecorresponds to a store and may open an application associated with thatstore. As yet another example, the device 346 may determine if there areany available coupons, deals, rewards, or other offers that areassociated with stores near the user when the card is removed. As yetanother example, the device 346 may associate a geographical locationwith the removal event, as described herein with respect to FIG. 3O-3P.

FIGS. 3J-3L illustrate another example accessory that is configured tomount to a device and/or a protective case of the device (e.g., on aback surface of the device or case). In particular, FIGS. 3J-3L depict adevice 354 (which may be in a protective case) and a battery accessory355 that is configured to be removably attached to a surface 357 (e.g.,a back surface) of the device 354. The device 354 may be or may be anembodiment of the device 100, and may be the same as or similar to thedevice 100.

The battery accessory 355 may include a near-field wirelesscommunication antenna 356 that is detectable by the near-field wirelesscommunication system of the device 354. The battery accessory 355 may beconfigured to charge a battery of the device 354 and/or otherwiseprovide power to the device 354. The battery accessory 355 may providepower to the device 354 via a cable, or it may include a wirelesscharging system comprising an output coil configured to inductivelycouple to a charging coil of the electronic device 354 when the batteryaccessory 355 is removably attached to the device 354.

The battery accessory 355 may also include magnetic attachment features362 that are configured to removably attach the battery accessory 355 tothe device 354 via complementary magnetic attachment features 363 of thedevice 354. The magnetic attachment features 362, 363 may includemagnets, ferromagnetic materials, or the like. The magnetic attachmentfeatures 362, 363 and the charging coils of the battery accessory 355and the device 354 may be embodiments of the corresponding componentsdescribed with respect to FIGS. 2A-2B.

FIG. 3K shows the battery accessory 355 removably attached to thesurface 357 of the device 354. As described for other near-fieldwireless enabled accessories, in response to detecting that the batteryaccessory 355 has been attached to the device 354, the device 354 maytake an action or change a mode of operation. In the case of attachingthe battery accessory 355, the device 354 display a graphical object(e.g., a notification object) providing information about the batteryaccessory 355 and/or its operation with respect to the device 354.

FIG. 3L, for example, illustrates an example graphical object 364 thatmay be displayed by the device 354 in response to the device 354detecting that the battery accessory 355 has been attached to the device354. The graphical object 364 may be displayed as a box that overliesanother graphical user interface, application, or the like, and maydisappear after a certain time or be dismissed by the user. Thegraphical object 364 may display information such as a battery chargelevel of the battery accessory 355 and an estimated time it will takefor the battery accessory 355 to fully charge the device 354 (as shownin FIG. 3L). Other information may also be displayed, such as a name ornickname of the battery, a name of an owner of the battery, a batteryhealth of the battery accessory 355, a predicted charge level of thedevice 354 if the battery accessory 355 remains on the device 354 for acertain period of time (e.g., 1 hour=60% charge; 2 hours=100%), or anyother suitable information.

The device 354 may also initiate actions in response to detecting theremoval of the battery accessory 355. For example, the device 354 maydisplay a graphical object (which may be similar in appearance andfunction to the graphical object 364, and may include a remaining chargeof the battery accessory 355, an amount of charging time that thebattery accessory 355 will require for a full charge. As anotherexample, the device 354 may associate a geographical location with theremoval event, as described herein with respect to FIG. 3O-3P.

FIGS. 3M-3N illustrate an example in which a device detecting aparticular type of case may cause the device to display informationrelevant to that case. For example, as shown in FIGS. 3M-3N, a case 365may include multiple pieces or components that need to be assembled in aparticular way in order to secure the case to the device. Accordingly,the case 365 may include a near-field wireless communication antenna sothat the device can detect when the case 365 is being used and provideassembly instructions and/or other information to the user.

As shown in FIG. 3M, the case 365 includes a back member 367 and aperipheral member 366. The back member 367 is configured to cover andprotect the back of the device 100, while the peripheral member 366protects the sides of the device and holds the back member 367, thedevice 100, and the peripheral member 366 together. The back member 367may include a near-field wireless antenna 368 that is detectable by thedevice 100, as described herein. The peripheral member 366 may have aseam or discontinuity to allow the peripheral member 366 to expand toaccept the device 100 and the back member 367. To secure the case 365,the peripheral member 366 may be closed by closing the seam ordiscontinuity as indicated by arrow 370. The peripheral member 366 mayalso include a latch member 369 that secures the peripheral member 366in the closed configuration.

FIG. 3N illustrates the case 365 in an initial stage of assembly. Inparticular, the device 100 may be placed on the back member 367, whichmay result in the near-field wireless communication antenna 368 of theback member 367 being detected by the near-field wireless communicationsystem of the device 100, which in turn causes a graphical output 371 tobe displayed on the display 104 of the device 100. The graphical output371 may include any suitable text and/or graphical content. In someimplementations, the graphical output 371 includes assembly instructionsfor the case 365. For example, the graphical output 371 may illustratehow to close the seam and secure the latch member 369 to lock theperipheral member 366 around the back member 367 and the device 100. Insome cases, the latch member 369 may include a near-field wirelesscommunication antenna, and the device 100 may be able to detect when thelatch member 369 is in a latched or secured position. In response todetecting that the latch member 369 is in the latched or securedposition, the device 100 may display a graphical object indicating tothe user that the case has been properly and/or completely assembled.

Instead of or in addition to displaying assembly instructions, thedevice 100 may display other graphical objects or graphical userinterfaces, or otherwise change its mode of operation, in response todetecting that it is being used with the case 365. For example, the case365 may be a ruggedized case that is intended for use during outdoorrecreational activities. Accordingly, the device 100 may initialize afitness application, GPS application, or other application that reflectsa probable upcoming activity of the user. As described above, the device100 may use other sensors or information to determine what (if any)applications or operational modes to initiate while the device 100 is inthe case 365. For example, if the device 100 detects that the ruggedizedcase 365 is being attached to the device 100 proximate a trailhead, thedevice 100 may initiate an application associated with hiking (e.g., aGPS application, a fitness tracking application, or the like). If thedevice 100 detects that the ruggedized case 365 is being attached to thedevice 100 proximate a downhill ski facility, the device 100 mayinitiate an application associated with skiing (e.g., a ski trackingapplication, a map of the ski facility, or the like).

As described above with respect to the card wallet accessory and thebattery accessory, a device may take certain actions upon detecting theremoval of an accessory from the device (or upon removal of the devicefrom a case, dock, or any other accessory). For example, the device maylog the location of the device when the accessory was removed. Thisinformation may be helpful for alerting the user to unintendeddetachments of accessories and finding lost accessories. FIGS. 3O-3Pdepict a device 100 being used with an accessory 372 (which mayrepresent the card wallet accessory 347, the battery accessory 355, orany other near-field wireless enabled accessory).

FIG. 3O shows the accessory 372 and the device 100 attached. When theaccessory 372 is removed from the device 100 (or the device 100 andaccessory 372 are decoupled), the device 100 may detect the removal bydetecting the absence of the near-field wireless antenna of theaccessory 372. In response to detecting the removal of the accessory372, the device 100 may save information about the removal event. Forexample, the device 100 may determine the location of the device at thetime of the removal of the accessory 372, and a time of the removal ofthe accessory 372. In some cases, the device 100 will display this (orother) information to the user upon removal. For example, as shown inFIG. 3P, the device 100 may display a map 373 with a graphical indicator375 representing the location where the accessory 372 and the device 100were separated. The device 100 may also display textual information 374.In some implementations, the textual information 374 provides textindicating the location (e.g., an address, latitude/longitudecoordinates, or the like), the time of removal, and optionally otherinformation.

The information about the removal of the accessory 372 may be displayedto the user substantially immediately after detecting the removal event,or it may not be displayed and instead be logged for later retrievaland/or viewing by the user. In either case, the information may bestored so that the user can retrieve and view the information as needed.

FIGS. 3A-3P show examples of protective cases and other accessories thatuse a passive antenna to change an operational mode of an electronicdevice when used with the device. Similar principles may apply to deviceholders that are configured to hold or support a device during anactivity. FIG. 4 illustrates two examples of device holders or docksthat may include near-field wireless communication antennas to changethe operational mode of the device 100.

FIG. 4 illustrates the device 100 while displaying a first graphicaluser interface 404, which may be the primary graphical user interface ofthe device 100, such as graphical user interface 128 (FIG. 1B). FIG. 4also shows the device 100 mounted to a dock 400 in a car. The dock 400may include a near-field wireless communication antenna that causes thedevice 100 to switch from displaying the first graphical user interface404 to displaying a second graphical user interface 401 that is tailoredfor use while driving (e.g., the device may cease displaying the firstgraphical user interface and begin displaying the second graphical userinterface). As with the other accessories described herein, thetransition may be automatic and seamless to the user—simply placing thedevice in the dock 400 (e.g., so that the device is positioned on orheld by the dock) may cause the device 100 to transition to thecar-specific graphical user interface.

The graphical user interface 401 may include audio controls that arelarge and easy to see and touch while the user is driving. The graphicaluser interface 401 may also include a map or navigation view. In somecases, the graphical user interface 401 may include large, easy to readicons for various different applications or functions (e.g., radio,telephone, map, messages, etc.). The device 100 may also change otherdevice settings as a result of detecting that it has been mounted to thedock 400. For example, the device 100 may enter a “do not disturb” modethat may reduce the possibility of distraction while driving. This mayturn off message notifications (e.g., text messages, emails, applicationnotifications, etc.) so that the user is not tempted to type responsesor read text-based messages while driving.

FIG. 4 also illustrates the device 100 mounted to a dock 402 on abicycle. The dock 402 may include a near-field wireless communicationantenna that causes the device 100 to cease displaying the firstgraphical user interface 404 and instead display a second graphical userinterface 403 that is tailored for use while cycling. For example, thegraphical user interface 403 is displaying a speed, a heart rate, and adistance travelled. In some cases, placing the device 100 in thebike-mounted dock 402 may cause the device 100 to initiate anapplication, such as an activity tracking application, a biometricmonitoring application (e.g., a heart-rate monitor), a map orpositioning application (e.g., a GPS application), or the like. In somecases, placing the device 100 in the bike-mounted dock 402 (or otherexercise-related dock or accessory, such as a dock on a running strolleror stationary bike, or arm-mounted carrying case) causes the device 100to display an affordance that, when selected by a user, causes thedevice to begin recording a workout associated with the exerciseequipment associated with the dock (e.g., an outdoor bike ride, a run,an indoor bike ride). As another example, placing the device 100 in thebike-mounted dock 402 (or other exercise-related dock or accessory)causes the device 100 to display a list of multiple affordances (e.g.,outdoor bike ride, indoor bike ride, outdoor run, etc.) from which auser may select to initiate a workout recording.

Accordingly, the graphical user interface 403 may be the graphical userinterface of that particular application. In some cases, the graphicaluser interface 403 does not correspond to any single application, butinstead displays outputs from various different applications orfunctions that are being executed by the device. For example, the speedoutput and the distance travelled may be provided by a GPS orcycling-specific application, while the heart rate output is provided bya biometric monitoring function or application. The graphical userinterface 403 may use the data from these applications without executingor displaying the dedicated graphical user interfaces of thoseapplications.

While the graphical user interface 403 is shown as having only outputs,it may also or instead include selectable inputs, such as audio controlsthat are large and easy to see and touch while the user is riding, largeicons for various different applications or functions (e.g., radio,telephone, map, messages, etc.). The device 100 may also change otherdevice settings as a result of detecting that it has been mounted to thedock 402. For example, the device 100 may enter a “do not disturb” modethat may reduce the possibility of distraction while cycling. This mayturn off (or mute) message notifications (e.g., text messages, emails,application notifications, etc.) so that the user is not tempted to typeresponses or read text-based messages while cycling. In someimplementations, when the device 100 is being used with other docksand/or accessories, such as home-based docks, protective cases, chargingdocks, wallet accessories, auxiliary batter accessories, etc., messagenotifications are not turned off or muted (e.g., they are displayed orotherwise provided to the user).

The device 100 may be mounted to other types of docks. For example, thedevice 100 may be mounted to docks that are integrated with or otherwiseassociated with exercise equipment such as stationary bicycles, rowingmachines, elliptical machines, stair-climbing machines, or the like.When mounted to exercise equipment, the device 100 may detect the typeof exercise equipment it is mounted to and initiate a coachingapplication or service that is relevant to that particular equipment.The device 100 may also use additional information to determine whattype of coaching application or service to use, or whether to display auser interface that does not include a coaching service or interface.For example, the device 100 may use the device's location to determineif it is mounted to the user's home stationary bike or a stationary bikeat a fitness studio. If it is mounted to the home stationary bike, thedevice 100 may initiate a coaching application or service, and if it ismounted to a bike at a fitness studio, the device may not initiate thecoaching application (reflecting the fact that the fitness studio mayhave live coaches, for example).

The accessories shown in FIGS. 3A-4 may have features and physicalcharacteristics that make them suited to certain uses. For example, aruggedized case may be targeted for rough work environments, and a sportcase may have straps so the case can be worn during workouts. Whilethese accessories may cause a device to change its operation usingnear-field wireless communication systems, they do not communicate withor interact with the device 100 in other ways. However, accessories thatuse near-field wireless communication systems may also have othercomponents, systems, or mechanisms that interact or communicate with thedevice 100 to expand the functionality of the accessory and/or thedevice 100.

FIG. 5 illustrates two examples of protective cases that use near-fieldwireless communications to cause the device 100 to change its mode ofoperation and also include input systems that wirelessly communicatewith the device 100 and provide auxiliary inputs for a user. Forexample, FIG. 5 shows the device 100 not attached to an accessory orinserted in a case, and displaying a first graphical user interface 501,which may be the primary graphical user interface of the device 100,such as graphical user interface 128 (FIG. 1B). FIG. 5 also shows thedevice 100 after it has been inserted into a camera case 500. Similar tothe other protective cases described herein, the camera case 500 mayinclude a near-field wireless communication antenna that causes thedevice 100 to cease displaying its first graphical user interface andreplace it with a second graphical user interface. In this case, becausethe case 500 is configured to facilitate the use of the device's camerafunctions, the second graphical user interface may be an image-captureinterface 508. The image-capture interface 508 may include a preview ofthe scene at which the device's camera is aimed, as well as otherselectable regions or input areas for controlling aspects of the camerafunctions (e.g., flash settings, aperture, shutter speed, white balance,image-capture type (e.g., video mode, still image mode, slow-motionmode), self-timer settings, shutter button, front/back camera selector,or the like. The device 100 may transition from the first graphical userinterface 501 to the media-capture interface 508 (e.g., a still imagecapture user interface or a video capture user interface) when thedevice 100 is inserted into the camera case 500, or if the device'sdisplay is off when the device 100 is inserted into the camera case 500,the display may automatically turn on and immediately display theimage-capture interface 508.

The camera case 500 may also include auxiliary input systems, such asbuttons 502, that are configured to control image-capture functions ofthe device 100. For example, one of the buttons 502 may act as a shutterbutton to capture an image or begin or end a video recording. As anotherexample, the buttons 502 may control zoom functions, aperture settings,shutter speed, or any other image-capture functions. The camera case 500may also have a button mechanism 506 that allows a user to actuate abutton of the device 100 itself. For example, the button mechanism 506may include a movable button member (or membrane or material) thattransfers force from a user's finger to the button 108 of the device 100(FIG. 1A) to mechanically actuate the button 108. In some cases, whenthe device 100 is inserted into the camera case 500, the detection ofthe near-field wireless communication antenna of the camera case 500causes the device 100 to re-map the input from the button 108 from afirst function, such as locking the phone and/or deactivating thedisplay, to a second function, such as a shutter button. This re-mappingmay occur whenever the device 100 is in the camera case 500 and thedevice 100 is in an image-capture mode. That is, a user may leave animage-capture mode (and thus leave the image-capture interface 508) anduse the device 100 in other modes (e.g., using the primary graphicaluser interface 501) while the device 100 remains in the camera case 500.Under such circumstances, the device may revert the button 108 to adefault function, and may re-map the buttons 502 to other functions.When the user re-initializes the image-capture interface, the device 100may once again use the buttons 108, 502 to control aspects of theimage-capture functions of the device 100.

Actuation signals from the buttons 502 may be detected by the device 100in various ways. In some cases, the buttons 502 use near-field wirelesscommunication techniques to provide inputs to the device 100. Forexample, the buttons 502 (or any other type of input system) may includean actuation member configured to be actuated by a user. The actuationmember may be any component that is actuated by a user, such as rigidbutton member, a membrane, or the like. The buttons 502 may furtherinclude a passive antenna, such as a near-field wireless communicationantenna. When the actuation member is actuated by the user (e.g.,pressed), the buttons 502 may cause the near-field wirelesscommunication antenna to become detectable by the electronic device. Forexample, when the buttons 502 are in an unactuated state, the near-fieldwireless communication antenna may be in a state or configuration thatcauses the antenna to not detectable by the device 100. This may becaused by the antenna being electrically decoupled from other circuitelements, grounded, electrically coupled to other circuit elements, orotherwise put into a state where the near-field wireless communicationsystem of the device 100 does not (and/or cannot) detect the antenna. Inresponse to the actuation member being actuated by the user, the passiveantenna may become detectable by the electronic device. Moreparticularly, the user actuating the actuation member (e.g., by pressingit with a finger or other object) may change the electricalconfiguration of the antenna and/or associated circuitry in a mannerthat makes the antenna detectable by the device. For example, pressingthe actuation member may cause an electrical contact to close, therebyconnecting the antenna to a circuit element (e.g., a capacitor, aninductor, a resistor, etc.) to make the antenna detectable by thenear-field wireless communication system of the device 100. In anotherexample, pressing the actuation member may cause an electrical contactto open, thereby decoupling the antenna to an electrical ground. Othertechniques may also be used to cause the antenna to switch between adetectable state and an undetectable state. Further, other techniquesmay be used to wirelessly communicate actuation signals from the buttons502 to the device 100, such as other wireless communication protocols(e.g., Bluetooth, WIFI), acoustic signals (e.g., audible, ultrasonic),light, or the like.

The device 100 may be configured to execute an operation in response todetecting the passive antenna with the device's near-field wirelesscommunication system. For example, when the user presses or actuates oneof the buttons 502, the antenna associated with the button may bedetected by the near-field wireless communication system of the device100. The antenna may communicate some information to the device 100 thatcauses the device to perform a function such as capture an image, zoomin or out on a scene or subject, change a camera setting (e.g.,aperture, shutter speed), or the like. The information communicated tothe device 100 by the antenna may be a command to execute a particularfunction, an identifier that the device 100 uses to lookup an associatedfunction or command, or any other suitable information.

Because the camera case 500 may include auxiliary inputs (or mayotherwise cause a user to operate the camera function differently thanwhen the device 100 is not in the camera case 500), the image-captureinterface 508 may be different than an image-capture interface that isdisplayed when the device 100 is not used with the camera case 500. Forexample, a default image-capture interface for use without the cameracase 500 may include selectable shutter button objects and other settingcontrols on the display of the device. Because the camera case 500 mayinclude physical buttons to control these functions, in someimplementations separate display-based controls for the functions areomitted from the image-capture interface 508 (while in otherimplementations, display-based controls for the functions are displayedon the image-capture interface 508, such that the user can use thedisplay-based controls and/or the physical buttons. The image-captureinterface 508 may differ from a default image-capture interface in otherways as well. The image capture interface 508 is shown displayingshapes, though the shapes represent a live preview of the camera (e.g.,the image the camera will capture when an image capture command (e.g.,shutter button) is received).

Gaming case 510 is another example case that may use a near-fieldwireless communication antenna to cause a device to change to anoperating mode that is contextually relevant to the intended use ofcase, and also use near-field wireless communication systems to provideauxiliary inputs that are contextually relevant to the intended use ofthe case. For example, the gaming case 510 may have a near-fieldwireless communication antenna that causes the device 100 to enter agaming mode, which may include transitioning from a first graphical userinterface to a gaming graphical user interface 516. In someimplementations, the gaming graphical user interface 516 is a selectionscreen of gaming applications (represented by the application icons withthe triangle, circle, and square shapes) that a user may select, thoughthe gaming graphical user interface 516 may be any other type ofinterface. For example, attaching the gaming case 510 to the device 100may cause the device 100 to launch a single gaming application (whichmay be selected by the user), thereby causing that game's dedicatedgraphical user interface to appear.

Like the camera case 500, the gaming case 510 may include auxiliaryinputs 512, 514 that use near-field wireless communication antennas tosignal input events to the device 100. In some implementations, theauxiliary input 512 is a directional pad (e.g., a generally plus-shapedinput member that can be used to provide directional inputs), ajoystick, an analog controller, or the like. In some implementations,the auxiliary inputs 514 are buttons. The auxiliary inputs 512, 514 mayuse the same or similar techniques as the buttons 502 to activate and/ordeactivate near-field wireless communication antennas.

The device 100 may be configured to dynamically re-map the auxiliaryinputs 512, 514 based on the game, application, operating mode, orgraphical user interface that is active on the device 100. For example,when the user places the device 100 into the gaming case 510, the device100 may enter a gaming mode or graphical user interface, and theauxiliary inputs 512, 514 may be mapped to gaming inputs (e.g., tocontrol a character or other aspect of a game). If the user exits thegaming mode while the device 100 is still in the gaming case 510, theauxiliary inputs 512, 514 may be re-mapped to other functions. Forexample, the directional pad 512 may control the position of a cursor onthe display or change a selected object, and the buttons 514 may selectitems, launch applications, switch the device between differentapplications or user interfaces, or the like. When the user returns tothe gaming mode, the auxiliary inputs 512, 514 may be re-mapped to thegaming functions.

While several examples of protective cases are described above, theseare merely some of the numerous types of accessories, and associatedchanges to the operating mode of the device, that may use near-fieldwireless communication techniques to automatically customize theoperation of a device. As one example of another accessory, a protectivecase may include a keyboard that wirelessly communicates with thedevice. When the device 100 is positioned in the case with the keyboard,the device 100 may change a setting so that an on-screen keyboard is notdisplayed when text input fields are selected or available, and so thatinputs from the case's keyboard are used for text input. The device 100may change its mode of operation in other ways, including changing anauto-correct model and/or algorithm (e.g., from one that is tailored totouch-screen based inputs to one that is tailored for physical keyinputs from the keyboard), changing sound and/or tactile outputsassociated with key presses, and the like. The device 100 may alsoinitiate a pairing sequence or otherwise initialize wirelesscommunication with the keyboard upon detecting the keyboard case. Thekeyboard may communicate with the device using any suitablecommunication technique or protocol, including wireless communicationssuch as WIFI, Bluetooth, near-field wireless communications, or thelike. In some implementations, the keyboard communicates with the devicevia a direct physical connection (e.g., a wired connection). In somecases, the keyboard may be associated with a keyboard dock orstand-alone keyboard instead of a protective case. In such cases, thenear-field wireless communication system of the device 100 may detectwhen the device 100 is docked on the keyboard or otherwise in proximityto the keyboard.

Another example protective case may include a battery that may rechargethe device 100 (either via physical connectors or wirelessly) when thedevice 100 is in the case. Upon the device 100 being inserted into thecase or otherwise used with the battery, the device 100 may display anotification indicating that a battery has been attached and optionallyproviding selectable inputs to control aspects of a charging function(as shown with respect to FIG. 2A). The device 100 may also record thelocation of the device 100 when the battery-enabled protective case wasattached to or removed from the device 100.

Accessories need not be protective cases that enclose or cover thedevice 100. For example, a card-holder or wallet-type accessory may beconfigured to attach to a device (or to a protective case), and thedevice 100 may use its near-field wireless communication system todetect when the card-holder accessory is attached to and removed fromthe device. The device 100 may customize a graphical user interface inresponse to detecting that the card-holder accessory has been attached(e.g., changing a background color or image of a primary graphical userinterface to match a color of the accessory, or changing a color schemeor background of a graphical user interface of a digital walletapplication to match the card-holder accessory). The device 100 may alsouse the near-field wireless communication system to help a user identifywhen and where the card-holder accessory is removed from the device. Forexample, upon the device 100 detecting that the card-holder accessoryhas been removed from the device 100, the device 100 may record thecurrent time and the location of the device 100 (e.g., from a GPS orother positioning system). This information may then be provided to auser to help the user locate the card-holder accessory or at least knowwhen and where the card-holder accessory was lost or removed. Forexample, a notification may be provided on the display of the devicethat shows the time and location (e.g., on a map) when the accessory wasremoved from the device 100.

Some accessories, such as some of the cases described above, may beconfigured to cause the device 100 to enter a particular operating modeor initiate a particular application that is tailored for use with thatcase. For example, the camera case 500 may cause the device to initiatea camera application. In some cases, a user may be able to customize howa device behaves, such as what is presented on its graphical userinterface, when it is used with different accessories. For example, thedevice 100 may allow the user to create multiple different auxiliarygraphical user interfaces that each include desired interfacecomponents. The user can also associate the auxiliary graphical userinterfaces with respective accessories. For example, the user can createone auxiliary graphical user interface that is activated (e.g.,displayed instead of a primary graphical user interface) when the deviceis placed on a dock in a bedroom, and a second, different graphical userinterface that is activated when the device is placed on a dock in akitchen. In some cases, the user can create numerous different auxiliarygraphical user interfaces for numerous different use cases andaccessories.

The auxiliary graphical user interfaces may be created by allowing auser to select from a group of candidate graphical objects. FIG. 6, forexample, illustrates an example group of candidate graphical objects,including an audio control object 600, a home automation object 602, arecipe object 604, a timer object 606, a calendar object 608, a channelguide and selection object 610, a clock object 612, a weather object614, and a news-feed object 616. In order to create an auxiliarygraphical user interface, the user may select graphical objects from thegroup of candidate graphical objects, associate them with particularlocations on the display 104 of the device 100 (e.g., defining auser-defined arrangement), and associate the auxiliary graphical userinterface with a particular accessory. The graphical objects may haveinput objects, output objects, or both. Notably, the user may definenumerous auxiliary graphical user interfaces each with different objectsor different combinations of objects (or even with the same objects in adifferent user-defined arrangement). For example, one auxiliarygraphical user interface may include the audio control object, whileanother may lack the audio control object. By providing suchflexibility, users can produce highly customized and relevant auxiliaryuser interfaces for use with numerous different docks and accessories.

In some implementations, auxiliary graphical user interfaces areassociated with specific docks or other accessories. For example, insome implementations, a user creates an auxiliary graphical userinterface (e.g., by selecting a set of graphical objects from thecandidate graphical objects), and associates the created auxiliarygraphical user interface with a dock (e.g., by creating the auxiliarygraphical user interface while the device is on the dock, by placing thedevice on the dock after creating the auxiliary graphical userinterface, by manually associating the dock with the created auxiliarygraphical user interface, or the like). Thereafter, when the device isplaced on the dock, the user-created auxiliary graphical user interfaceis displayed. The same process may be used to create other customizedauxiliary graphical user interfaces that are associated with otherdocks.

The audio control object 600 may include audio control input objects(“audio control inputs”) for controlling audio playback functions of thedevice 100 or any other device that the device 100 can control. Forexample, the audio control inputs of the audio control object 600 may beconfigured to control audio of a network-connected audio system that thedevice 100 can control using network communications. The audio controlobject 600 may also have output objects, such as an indicator of thecurrently played or queued media, album art, or the like.

The home automation object 602 may include input objects that allow theuser to control network-connected home automation systems, such asalarms, lighting, audio systems, HVAC systems, and the like. The homeautomation object 602 may also include output objects that indicate thestate of interconnected systems, such as the lights, door sensors,window sensors, and the like. As noted above, in some implementations, adock can be associated with a particular virtual room or environment ina home automation platform. Accordingly, when the device is placed on adock associated with a particular virtual room or environment, the homeautomation object 602 may display controls for devices that are alsoassociated with the particular room or environment. Thus, for example, ahome automation object 602 that is displayed when the device is placedon a dock associated with and/or assigned to a “dining room” environmentin the home automation platform can display controls for operating thelights of the dining room, while a home automation object 602 that isdisplayed when the device is placed on a dock associated with and/orassigned to a “living room” environment in the home automation platformcan display controls for operating the lights in the living room, aswell as a television and an audio system. Accordingly, the user need notmanually select individual devices (e.g., a television, a set of lights,etc.) to associate with the home automation object (though in somecases, that is also an option). In some implementations, a homeautomation object in an auxiliary graphical user interface includesdifferent controls based on the time of day. For example, a homeautomation object in an auxiliary graphical user interface for a bedroomdock may display, when the device is placed on the dock during the day,controls for an audio system, and, when the device is placed on the dockduring the evening, controls for bedroom lights and a home alarm system.

The recipe object 604 may display cooking recipes or recipe lists. Therecipe object 604 may also provide a search interface for searching forrecipes. The timer object 606 may provide inputs for setting a timer andselecting timer settings (e.g., alert tones, volume, etc.), and maydisplay timer progress. The calendar object 608 may show a snapshot of auser's calendar items. The channel guide and selection object 610 maydisplay a list of channels, shows, show times, or other televisionprogram information. The channel guide and selection object 610 may alsoprovide input objects for controlling a television, DVR, DVD player, orthe like. The clock object 612 may display the current time. The weatherobject 614 may display current weather conditions and/or weatherforecasts. The news-feed object 616 may display news headlines orarticles.

The foregoing represents only some of the possible graphical objectsthat may be provided to a user to create auxiliary graphical userinterfaces. In some cases, more, fewer, or additional graphical objectsmay be provided as well. The graphical objects may be associated with oruse functions of other applications that are executed by the device 100.For example, a timer application (which may have its own separategraphical user interface) may provide timing functions for the timerobject 606. In some cases, the functions of multiple differentapplications are included in a single graphical object. For example, thehome automation graphical object 602 may use functions provided by alighting application (on the device 100) to control lights, andfunctions of a separate thermostat application (on the device 100) tocontrol the HVAC system.

Associating the auxiliary graphical user interface with a particularaccessory may include associating the auxiliary graphical user interfacewith an identifier of a near-field wireless communication antenna of theaccessory. For example, when a device is placed on or used with anaccessory for the first time, the device may prompt the user to createan auxiliary graphical user interface for use with that accessory. Thedevice may then store the association between the auxiliary graphicaluser interface and the accessory so that when the device detects theaccessory in the future (e.g., using the near-field wirelesscommunications described herein), the device will transition fromdisplaying a first graphical user interface (e.g., whatever graphicaluser interface is active at that time) to displaying the auxiliarygraphical user interface associated with that accessory.

In some cases, instead of an auxiliary graphical user interface thatincludes a set of user-selected graphical objects, a user may associatea particular accessory or dock with a particular application. Forexample, a device may include a dedicated application for a socialnetwork, a telephone, a video phone, a music player, or the like. Theuser may select any given application to be executed and/or initializedwhen the device is placed in a particular dock. Thus, as one example,the user may associate a video phone application with a dock that sitson the user's desk. Whenever the user places the device in that dock,the video phone application may be initialized (including, for example,causing the device to display the graphical user interface of the videophone application). In some cases, a phone or video phone applicationmay be configured to initiate a call or an audio and/or video streamwith another device in response to the device being placed in aparticular dock. For example, when the user places the device in a dockat the user's work desk, a live video stream of the user's home securitycamera (or any other electronic device) may be displayed on the device.As another example, when the user places the device on a dock at theuser's home desk, a video call with another person may be initiated. Asdescribed above, in some implementations, the particular application(s),control(s), and/or graphical object(s) that are executed and/ordisplayed in response to the device being placed on or used inconjunction with a dock or other accessory are based on an assignment ofthe dock or other accessory to a room in a home automation platform.Thus, for example, when a device detects that it is placed on a dockthat is associated with or assigned to an “office” environment in a homeautomation platform, the device can execute an application or showcontrols that are also associated with the “office” environment. In somecases, multiple docks or accessories may be associated with the sameroom or environment in a home automation platform. In such cases, thedifferent docks, even when associated with the same room or environment,may cause a device to execute or display different application(s),control(s), and/or graphical object(s). In some implementations, theparticular application(s), control(s), and/or graphical object(s) thatare displayed and/or executed are based on a property or type of dock(e.g., an alarm clock dock in a bedroom may cause alarm controls to bedisplayed, while a charging dock in the bedroom may cause lighting andaudio controls to be displayed), or based on a user selection (e.g., auser can specify that a first bedroom dock will cause a first set ofapplication(s), control(s), and/or graphical object(s) to be displayedand/or executed, and a second bedroom dock will cause a second set ofapplication(s), control(s), and/or graphical object(s) to be displayedand/or executed).

In some cases, multiple individuals may configure their devices anddocks to initiate a video call or video conference whenever two or moreof the devices are placed on particular docks. For example, two usersmay configure their devices so that if one user places his or her deviceon a particular dock while the other user's device is also on a dock, avideo call (e.g., a live or streaming video feed) is automaticallyinitiated (e.g., without further user input). The video call may beterminated automatically upon either of the devices being removed fromtheir respective docks. This may provide an easy and efficient way forfamily, friends, and coworkers to communicate with one another. Whilethe foregoing example describes a two-person communication link, asimilar technique may be used for more than two users. For example, agroup of coworkers may each configure their device to initiate a videoconference when their device is placed on a dock at their work place. Inthis way, they may be able to instantly collaborate with anyone else intheir company or work group that is also available at that time. Theuser may simply remove their phone from the dock when they no longerneed or want to communicate with that group. A user may even configuretheir device to join a different video conference when it is placed on adifferent dock. Accordingly, a user can communicate with differentgroups simply by moving their device to a different dock. While theforegoing examples are described primarily with respect to videoconferences or video calls that are initiated by placing a device on adocking accessory, the same principles may be applied to audio-onlycommunications (instead of video) and other types of accessories such asprotective cases, charging docks, charging mats, vehicle-mounted docksor holders, or the like.

FIG. 7 illustrates how various different auxiliary graphical userinterfaces may be displayed on the device 100 based on what accessory ordock the device 100 is placed on. Each dock shown in FIG. 7 may includea near-field wireless communication antenna that allows the device 100to detect when it has been placed on the support structure. Further,each dock may include a support structure that is configured to hold thedevice in a viewable orientation when the dock is on a surface of anobject (e.g., structure 701 of the dock 700). The surface of an objectmay correspond, for example, to a surface of a table, counter, desk,nightstand, dresser, or any other suitable object. In this way thedevice can be viewed and interacted with, including allowing the user totouch the device to provide inputs (by pressing buttons, providing touchor stylus inputs on a touch sensitive surface, or the like). Further,the support structure may allow a user to simply place the device ontothe support structure and remove it from the support structure (andconsequently cause it to initiate a different operating mode and/orgraphical user interface) without additional steps such ascommunicatively pairing the devices, mechanically securing the device toor in the dock, aligning and coupling electrical connectors, or thelike.

Returning to FIG. 7, when the device 100 is placed on the first dock700, the device 100 may detect, with its near-field wirelesscommunication system, the antenna of the first dock 700 and therebydetermine that it is in proximity to (e.g., placed on) the first dock700. The device 100 may then determine what mode of operation it shouldoperate in based on its proximity to the first dock 700 (e.g., whatauxiliary graphical user interface to display) and begin operating inthe mode of operation that corresponds to the first dock 700 (e.g., itmay display the graphical user interface that has been associated withthat dock). In the example shown in FIG. 7, the device 100 may display afirst auxiliary graphical user interface 710, which may include achannel guide and selection object (e.g., allowing a user to view andselect channels to view on a television) and a home automation object(e.g., allowing a user to control home automation systems such aslights, security systems, door locks, thermostats, etc.). Thesegraphical objects which may have been selected by the user to bedisplayed when the device 100 is in this particular dock. For example,the first dock 700 may be located in a user's living room or recreationroom where television channel selection and home automation controls areparticularly useful to the user. Of course, because a user can customizethe graphical user interface for any dock in any location, the contentsof the first auxiliary graphical user interface 710 are merely examplesand may be customized by a user to fit the user's particular needs for aparticular dock location.

The first auxiliary graphical user interface 710 may be displayed whenthe device 100 is placed on the dock 700 regardless of what wasdisplayed immediately prior. For example, if the device 100 is notdisplaying anything (e.g., the display 104 is blank), the display 104may turn on and immediately display the first auxiliary graphical userinterface 710. If the device 100 is currently displaying a primarygraphical user interface (e.g., the primary graphical user interface128, FIG. 1B), the device may cease displaying the primary graphicaluser interface and instead display the first auxiliary graphical userinterface 710.

When the device 100 is placed in a second dock 702, the device 100 maydetect, with its near-field wireless communication system, the antennaof the second dock 702 and thereby determine that it is in proximity to(e.g., placed on) the second dock 702. The device 100 may then determinewhat mode of operation it should operate in based on its proximity tothe second dock 702 (e.g., what auxiliary graphical user interface todisplay) and begin operating in the mode of operation that correspondsto the second dock 702 (e.g., it may display the graphical userinterface that has been associated with that dock). In the example shownin FIG. 7, the device 100 may display a second auxiliary graphical userinterface 712, which may correspond to a live video stream captured by aremote electronic device and sent to the device 100. More particularly,when the device 100 is placed on the second dock 702, a live video linkwith another device may be automatically initiated. The live video linkmay be with another similar device (e.g., a mobile phone, tabletcomputer, laptop computer) that allows two-way audio and videocommunications, or with a camera such as a security camera or webcam.Accordingly, the second auxiliary graphical user interface 712 maycorrespond to a video feed from another camera. As another example,instead of automatically initiating the live video link, placing thedevice 100 on the second dock 702 may cause the device 100 to display alist of contacts that a user can select to initiate a live video oraudio feed with the selected contact. The device 100 may also activate amicrophone or voice recognition scheme to accept a spoken command (e.g.,“call my mother”). As noted above, the second auxiliary graphical userinterface 712 may be displayed when the device 100 is placed on thesecond dock 702 regardless of what was displayed on the device 100immediately prior. For example, the device 100 may transition from ablank screen to the second auxiliary graphical user interface 712 orfrom another graphical user interface (e.g., a primary graphical userinterface) to the second auxiliary graphical user interface 712.

When the device 100 is placed in a third dock 704, the device 100 maydetect, with its near-field wireless communication system, the antennaof the third dock 704 and thereby determine that it is in proximity to(e.g., placed on) the third dock 704. The device 100 may then determinewhat mode of operation it should operate in based on its proximity tothe third dock 704 (e.g., what auxiliary graphical user interface todisplay) and begin operating in the mode of operation that correspondsto the third dock 704 (e.g., it may display the graphical user interfacethat has been associated with that dock). In the example shown in FIG.7, the device 100 may display a third auxiliary graphical user interface714, which may include graphical objects relevant to a kitchenenvironment. For example, in some implementations, the third auxiliarygraphical user interface 714 includes a recipe object that may allow auser to search for recipes, select from saved recipes, and read recipes.The third auxiliary graphical user interface 714 may also include atimer object, and/or a measurement conversion object.

Activation of the third auxiliary graphical user interface 714 may alsoconfigure the device to respond to spoken instructions (e.g., to scrollthe recipe or change between recipes, to control the timers, etc.) sothat the user does not need to touch to the device 100 to manipulate theuser interface during cooking, which may be unsanitary and may damagethe device 100. Further, an automatic display shutoff may be disabled sothat the display (and thus the recipe, timers, etc.) do not disappearwithout warning. Of course, other user-selected graphical objects may beused instead of or in addition to those shown in the third auxiliarygraphical user interface 714.

In some cases, docks that include support structures to hold the devicein a viewable orientation may also include input systems that areconfigured to wirelessly communicate with the device in response to theinput system being actuated by a user when the electronic device ispositioned on the support structure. For example, FIG. 7 shows anexample alarm clock dock 706 that includes input systems such as buttons720. The buttons 720 may be similar to those described with respect toFIG. 5. For example, actuation signals from the buttons 720 may bedetected by the device 100 in various ways. In some cases, the buttons720 use near-field wireless communication techniques to provide inputsto the device 100. For example, the buttons 720 (or any other type ofinput system) may include an actuation member configured to be actuatedby a user, as well as a passive antenna, such as a near-field wirelesscommunication antenna. When the actuation member is actuated by the user(e.g., pressed), the buttons 720 may cause the near-field wirelesscommunication antenna to become detectable by the electronic device. Forexample, when the buttons 720 are in an unactuated state, the near-fieldwireless communication antenna may be in a state or configuration thatis not detectable by the device 100. This may be caused by the antennabeing electrically decoupled from other circuit elements, grounded,electrically coupled to other circuit elements, or otherwise put into astate where the near-field wireless communication system of the device100 does not detect the antenna. In response to the actuation memberbeing actuated by the user, the passive antenna may become detectable bythe electronic device. (Other techniques may be used to wirelesslycommunicate actuation signals from the buttons 502 to the device 100,such as other wireless communication protocols (e.g., Bluetooth, WIFI),acoustic signals (e.g., audible, ultrasonic), light, or the like.)

As with the other docks shown in FIG. 7, placing the device 100 on thedock 706 may cause the device 100 to display a fourth auxiliarygraphical user interface 716. In some implementations, the fourthauxiliary graphical user interface 716 includes clock and/or alarm clockgraphical objects. Accordingly, the dock 706 may be suited for placementin a user's bedroom. The buttons 720 may be configured to control orchange settings of the clock and/or alarm clock graphical objects, suchas setting alarm times, snoozing an alarm, changing the displaybrightness (e.g., temporarily activating the display so that a user cansee the time during the night), or the like. This may improve theexperience of using the alarm functions of the device 100 by eliminatingthe need for a user to look at the display of the device to locate atouch-sensitive snooze button or otherwise control alarm functions.

In addition to transitioning to the fourth auxiliary graphical userinterface 716 in response to being placed on the dock 706, the device100 may also change other device settings. For example, where the dock706 is in a bedroom and being used as an alarm clock, the device mayalso change notification settings (e.g., turning off audible, visible,and/or tactile notifications of messages, events, etc.), change displaysettings (e.g., display brightness, display color content, etc.). Otherdevice customizations are also possible upon the device 100 detectingthat it is on the dock 706.

While FIG. 7 shows several example docks and associated auxiliary userinterfaces, other types of docks are also possible, including dockshaving different form factors, different targeted uses and/or locations,different arrangements and types of auxiliary input systems, and thelike. For example, a dock may include speakers (like the dock 118, FIG.1A) and may cause the device 100 to transition to an auxiliary graphicaluser interface that includes music or audio-control objects. As anotherexample, a dock without speakers may cause the device 100 to transitionto an auxiliary graphical user interface that includes music oraudio-control objects and also configures the device to control orconnect with a wireless speaker system.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured as a shared familydevice. This may include displaying a shared (e.g., among a family)calendar, task list, reminder list, or the like, as well as objects forcontrolling home functions such as security systems, a thermostat,lighting, music, or the like. In some implementations, sharedinformation (e.g., among a family) corresponds to information that isshared between accounts that are linked to a shared family account andshare access to information and/or content (e.g., a calendar, photos,contacts, etc.) and/or payment methods. In addition to transitioning tothe auxiliary graphical user interface, the device may also changedevice settings by restricting access to a single user's personalcontent (e.g., messaging applications and functions, etc.), changingnotification settings (e.g., turning off notifications or removingvisible message previews), and the like.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured as a voice-baseddigital assistant interface. This may include dynamically displayingtranscriptions of voice input, displaying content or graphical objectsrelated to voice-based commands issued to the device 100, or the like. Adock configured to customize the device for use as a digital assistantmay also include microphones and/or speakers that can communicate withthe device 100 to enhance the device's audio capabilities.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured to control anappliance that is wirelessly coupled to the device 100 or otherwiseconfigured to receive and/or respond to commands from the device 100.For example, an auxiliary graphical user interface for controlling awashing machine may include control objects tailored to the washingmachine's functions (e.g., water temperature, spin cycle level, cycletime, soil level). As another example, a user interface that isconfigured to control a coffee maker may include control objectstailored to the coffee maker's functions (e.g., brew start time, coffeestrength, grind size, water temperature). Of course, auxiliary userinterfaces may be tailored for use with other appliances and devices aswell.

Docks may also be provided at public places, businesses, or otherlocations where they may be used by many different users. Such docks maycause devices to transition to auxiliary graphical user interfaces thatare relevant to their locations and/or environments. For example, arestaurant may provide docks at their tables that cause devices todisplay a menu and/or ordering interface when the devices are placed onthe docks. As another example, an airport may have docks at each gatethat cause devices to display flight information for that gate. Asanother example, parks may have docks at points of interest that causedevices to display information or interactive applications related tothose points of interest. Shared docks such as those described above(and indeed any dock described herein) may also include wirelesscharging systems as described above with respect to FIGS. 2A-2B.

As described above, auxiliary user interfaces may be customized by auser and associated with a particular dock. In some cases, docks may beconfigured to trigger a pre-populated auxiliary graphical userinterface. For example, a dock may be sold as a “kitchen” dock, and thedock and/or devices that are usable with the dock may be configured totrigger an auxiliary graphical user interface that includes a recipeobject and a timer object. The user may use the default auxiliarygraphical user interface, or modify and/or change the auxiliarygraphical user interface in any manner (e.g., with different cooking orkitchen-relevant objects, or so that the dock can be used in an entirelydifferent context such as on the user's nightstand). Other types of“default” docks may also be provided and may trigger similarly tailoredauxiliary graphical user interfaces. For example, a “bedroom” dock may,by default, trigger an interface with an alarm clock object, and a“living room” dock may, by default, trigger a television control object.Of course, these default auxiliary graphical user interfaces may bereplaced or modified by the user using the modular user interface schemedescribed herein.

While the docks, cases, and other accessories described herein may causethe device to transition from one mode of operation to another(including, for example, transitioning from one graphical user interfaceto another, different graphical user interface), users may be able toselectively return to a previous or a different mode of operation (andassociated graphical user interface) while the device is stillassociated with an accessory. For example, when a device is placed onkitchen dock, thus triggering the transition to a cooking-based userinterface, the user may control the device to leave the cooking-baseduser interface and instead return to a primary graphical user interfacewhile the device remains on the dock. As another example, the user maycontrol the device to leave the cooking-based user interface and insteadinitiate a music-playback interface. A user may also be able to selectwhether or not a particular graphical user interface may be freelychanged. For example, if a user places a device in a child-proof case,they may not want the child to be able to freely return to the primaryuser interface. Accordingly, users may be able to select what auxiliarygraphical user interfaces (if any) may be freely available once a deviceis used with a particular accessory. A password or other authenticationmay be required in order to transition between auxiliary userinterfaces.

In some cases, the device 100 transitions from an auxiliary graphicaluser interface to a primary graphical user interface when the device 100is removed from a dock. For example, the near-field wirelesscommunication system of the device 100 may determine that the device isno longer in proximity to the dock based on ceasing to detect thenear-field wireless antenna of the dock. Upon ceasing to detect thenear-field wireless antenna of the dock, the device 100 may ceasedisplaying the auxiliary graphical user interface (or any othergraphical user interface associated with that dock) and begin displayingthe primary graphical user interface.

FIG. 8 depicts an example system in which electronic devices (e.g., afirst electronic device 800 and a second electronic device 802) may beused with various different accessories that cause the devices todisplay various visual indications when the accessories are attached toand/or detached from the devices. The first device 800 and the seconddevice 802 are examples of computer systems, such as the computer system3600 described herein with respect to FIG. 36. For simplicity, theelectronic devices (or computer systems) 800, 802 are referred to hereinas devices 800, 802.

As described above, accessories such as a charging dock 804, a walletaccessory 806, an auxiliary battery accessory 808, and protective cases810, 812 may be attached to the devices 800, 802. When the accessoriesare attached, and optionally detached, the detection of the attachmentand/or detachment may cause the devices to display, on the displays ofthe devices, visual indications that have some relevance to theaccessory. For example, the visual indications may have a shape and/orsize that is based on the shape and/or size of the attached accessory,or a color that is based on the color of the accessory. As anotherexample, the visual indications may include accessory-specificinformation, such as a graphical object that indicates the accessory'suse or function (e.g., a lightning bolt representing a battery chargingfunction), or a name (or other metadata) associated with the particularaccessory that is attached. In order to detect information about theaccessories, the devices 800, 802 may include near-field wirelesscommunication systems, as described above, that can detect and receiveinformation from the accessories via near-field wireless communicationantennas of the accessories. Information about the accessories may bedetermined using other techniques and/or systems instead of or inaddition to near-field wireless communications.

As described herein, one or multiple accessories may be attached to asingle device at one time, and each attached accessory may cause avisual indication to be displayed when the accessory is attached. Forexample, as described with respect to FIGS. 15A-15B, the charging dock804 may be attached to a device that is already attached to a protectivecase (e.g., the case 810). In this example, the case causes a visualindication to be displayed when it is attached to the device, and thecharging dock causes another visual indication to be displayed when itis attached to the device. As another example, a device may have aprotective case 810, an auxiliary battery accessory 808, and a chargingdock 806 attached (each of which, optionally, caused a visual indicationto be displayed when attached). As yet another example, a device mayhave a protective case 810, a wallet accessory 806, and an auxiliarybattery accessory 808 attached (each of which, optionally, caused avisual indication to be displayed when attached). In someimplementations, if multiple accessories are attached to a device at thesame time or substantially the same time, only one visual indication isdisplayed (e.g., the visual indication of the accessory closest to thedevice). In some implementations, if multiple accessories are attachedto a device at the same time or substantially the same time, a separatevisual indication for each of the attached accessories is displayed(e.g., one after the other).

In some implementations, in addition to displaying visual indications inresponse to detecting attachment of an accessory, a non-visual output isproduced in response to detecting the attachment of the accessory to thedevice. In some implementations, the non-visual output is produced evenwhen different types of accessories are attached. In someimplementations, the non-visual output is a tactile output, such as avibration, impulse, or the like. In some implementations, the non-visualoutput is an audio output, such as a beep, tone, melody, song, voicealert, or the like. In some implementations, both tactile and audiooutputs are produced in response to detecting attachment of theaccessory.

The accessories are configured to attach to the devices 800, 802 viaattachment mechanisms 814 in the devices, and corresponding attachmentmechanisms 818 in the accessories. In some implementations, theattachment mechanisms 814, 818 are magnetic attachment mechanisms toreleasably attach or couple the accessories and devices. For example, insome implementations, the attachment mechanisms 814 of the devices(e.g., 814-1, 814-2) include first magnets, and the correspondingaccessory attachment mechanisms 818 include second magnets or magneticmaterials (e.g., iron, steel, ferromagnetic materials, etc.) that areattracted to the first magnets. In some implementations, the attachmentmechanisms 814, 818 include or are associated with near-field wirelesscommunications systems, as described above, to facilitate the devicesreceiving information about the accessories. While the protective cases810, 812 are shown as including attachment mechanisms 818, attachmentmechanisms 818 may be omitted from the protective cases 810, 812, suchas in implementations where the cases have separate physical features toretain the cases to the devices. Even where the attachment mechanismsare omitted from the cases, the cases may include appropriate near-fieldwireless communications systems so that the devices can detectattachment of the cases to the devices.

The attachment mechanisms 814 may be located at a particular location inthe devices 800, 802. The locations of the attachment mechanisms may bedifferent for different devices. For example, in the first device 800,which may represent a mobile phone (or other type of computer system) ofa first size, the attachment mechanism 814-1 may be at a first location.By contrast, in the second device 802, which may represent a mobilephone (or other type of computer system) of a larger size than the firstdevice 800, the attachment mechanism 814-2 may be at a second location.The difference between the first and second locations may be understoodas being relative to the centroids of the devices. For example, theattachment mechanism 814-1 is located relatively closer to the centroidof the first device 800 than the attachment mechanism 814-2 is to thecentroid of the second device 802. In yet other cases, the location ofthe attachment mechanisms of differently sized or shaped devices issubstantially the same (e.g., they may both be located at a centroid ofthe device).

The attachment mechanisms 814, 818 may also have a particular shape. Forexample, the attachment mechanisms 814, 818 may have a generallycircular shape, as indicated by the broken-line circles in FIG. 8. Theshape may be defined by or represent a shape of the attachmentmechanisms within the devices. For example, the attachment mechanismsmay include an array of magnets that are positioned in a circulararrangement (e.g., along the circles shown in FIG. 8), or they mayinclude a single circular magnet having an outer periphery correspondingto the circles shown in FIG. 8. In some cases, the circles thatrepresent the attachment mechanisms 814, 818 may represent the areawhere the magnetic attraction occurs between the devices and theaccessories. For example, when the attachment mechanism 818 of thecharging dock 804 is brought into alignment with the attachmentmechanism 814-1 of the device 800 (e.g., such that the circles aresubstantially coincident with one another), the charging dock 804 mayattach to the device 800. While the instant figures illustrate theattachment mechanisms 814, 818 as circles, attachment mechanisms mayhave other shapes and/or configurations. For example, the attachmentmechanisms may have square or triangular shapes. In some cases, asdescribed herein, the shape of the attachment mechanism may berepresented in the visual indications that are displayed whenaccessories are attached to the devices.

In some cases, the accessories, when attached to the devices, have apredetermined orientation relative to the attachment mechanisms. Forexample, in some implementations, the attachment mechanisms 814, 818 areconfigured so that magnetic attraction between an attachment mechanism814 and an attachment mechanism 818 occurs only when the accessory isoriented in a particular orientation relative to the device. Forexample, the attachment mechanism 818 of the wallet accessory 806 isconfigured within the wallet accessory 806 such that it will only bemagnetically attracted to the attachment mechanism 814-1 in oneorientation (e.g., with the sides of the wallet accessory 806substantially parallel to the sides of the device 800). In some cases,misalignments of more than a threshold amount (e.g., 10 degrees, 20degrees) result in the accessory not attaching to the device, beingrepelled from the device, or being attracted towards the predeterminedorientation.

As noted above, when accessories are attached to the devices, visualindications may be displayed on the displays to inform users that theaccessories are attached, and optionally to convey information about theaccessories (or other relevant information). In some implementations,the visual indications include graphical elements that are based on orrepresentative of a physical property of the accessory. For example, thephysical property represented by a graphical element in a visualindication may be a physical dimension of the accessory, such as a size,shape, length, or width of the accessory. Other types of physicalproperties may include a color of the accessory.

Further, different accessories may cause a device to display differentvisual indications, where the different visual indications are based ona physical dimension of the particular accessory that is attached. Forexample, in accordance with a determination that an attached accessoryis a first accessory with first physical dimensions, a first visualindication that the accessory has been attached to the device isdisplayed, wherein the first visual indication indicates at least oneproperty of the first physical dimensions of the accessory (e.g., size,length, width, shape). In accordance with a determination that theaccessory is a second accessory with second physical dimensions that aredifferent from the first physical dimensions, a second visual indicationthat the accessory has been attached to the device is displayed, wherethe second visual indication indicates at least one property of thesecond physical dimensions, and the second visual indication isdifferent from the first visual indication. Examples of different visualindications being displayed in accordance with a determination of thetype of accessory are described herein. For example, FIG. 9C illustratesa visual indication displayed in accordance with a determination thatthe accessory is a charging dock (e.g., a first accessory), and FIG. 13Cillustrates a visual indication displayed in accordance with adetermination that the accessory is an auxiliary battery accessory(e.g., a second accessory with different physical dimensions than thefirst accessory).

FIGS. 9A-9C illustrate an example of how an accessory may attach to adevice via attachment mechanisms, and how the visual indicationdisplayed on the display of the device indicates at least one propertyof the physical dimensions of the accessory. FIG. 9A illustrates thedevice 800 with the representation of the attachment mechanism 814-1, aswell as the charging dock 804 with its attachment mechanism 818. Thecharging dock 804 may also include a cord 900 that couples to a powersource and provides electrical power to the charging dock 804, and thusto the device 800 when the charging dock 804 is attached to the device800.

FIG. 9B illustrates a front view of the device 800 with the chargingdock 804 attached to the back of the device 800. As illustrated in FIG.9B, the attachment mechanism 814-1 of the device 800 and the attachmentmechanism 818 of the charging dock 804 may be coincident with oneanother, and are thus represented by a single broken circle in FIG. 9B.FIG. 9B also shows, in dotted lines, the location and physicaldimensions of the charging dock 804 and the cord 900 along the back sideof the device 800. As noted above, the attachment mechanisms 814-1, 818may be configured so that the charging dock 804 attaches to the device800 in a predetermined orientation, such as with its cord 900 extendingvertically downward (relative to the orientation of FIG. 9B).

The device 800 detects attachment of the charging dock 804, and inresponse to detecting the attachment of the charging dock 804, displaysa visual indication 906 that the accessory has been attached to thedevice. The visual indication 906 may indicate at least one property ofthe physical dimensions of the charging dock 804. For example, thevisual indication 906 may include a graphical element 908 that has asize and a shape that is the same as the size and the shape of thecharging dock 804. As shown in FIG. 9C, for example, the graphicalelement 908 is a circle that has the same size and shape as the circularcharging dock 804. Further, the graphical element 908 indicates theactual location of the charging dock 804 on the device 800, as indicatedby the graphical element 908 coinciding with the dimensions of thecharging dock 804 in FIG. 9B. In this manner, the visual indication 906may illustrate, to the user, exactly where the accessory (here, thecharging dock 804) is located on the back of the device, as well as whatthe size and the shape of the accessory is, via the display on the frontof the device. The visual indication 906 may also include a fill region909 inside the graphical element 908. In some implementations, the fillregion 909 includes an opaque element, or a translucent element, or itmay be empty (e.g., graphical objects that are displayed on the displayand in the fill region 909 when the visual indication 906 is displayedmay be viewable through the fill region 909).

While FIG. 9C illustrates the graphical element 908 having the same sizeand shape as the attached accessory, any physical dimensions of theaccessory may be shown by a graphical element of a visual indication.For example, the graphical element may have a same width or length asthe accessory. In some cases, the graphical element may have onephysical dimension in common with the accessory, while in other cases ithas more than one physical dimension in common. For example, thegraphical element may have the same size and shape of the accessory, orit may have the same shape (e.g., a circle), but a different size (e.g.,a different diameter). As described herein, however, the selection ofthe property of the graphical element, such as the size, shape,location, color, or the like, may be based on the particular accessorythat is attached (as determined, for example, by a near-field wirelesscommunication system).

FIG. 9C also illustrates other example graphical elements that thevisual indication 906 may include. For example, in the example in FIG.9C, the visual indication 906 includes a graphical element 910 thatcorresponds to a location, size, and/or shape of the attachmentmechanism 814-1. For example, the attachment mechanism 814-1 of FIG. 9Chas a circular shape and a particular location in the device 800, andthe graphical element 910 has the same size and/or shape of theattachment mechanism 814-1, and may be located at the location of theattachment mechanism 814-1. With respect to the example in FIG. 9C, thegraphical element 910 is a circle that is positioned directly over thebroken lines representing the location, shape, and size of theattachment mechanism 814-1. In implementations where the attachmentmechanism 814-1 has a different location, size, and/or shape, thegraphical element 910 may match the different size, location, and/orshape. While the instant figures show dotted or broken linesrepresenting the locations of components or objects (e.g., thebroken-line circles representing the attachment mechanisms 814-1, 818and the location of accessories on a device), these are provided forreference and are not displayed as graphical elements on the display ofthe device. In some implementations, however, the dotted or broken linesare displayed as part of a visual indication when an accessory isattached.

In some cases, the graphical element 910 is displayed in other visualindications as well. For example, a visual indication that is displayedwhen a different accessory (e.g., the auxiliary battery accessory 808,wallet accessory 806, etc.) is attached to the device 800, a differentvisual indication may be shown on the display. The different visualindication may include a graphical element in common with the visualindication 906, such as the graphical element 910. In this way, multiplevisual indications include at least one common graphical element thatindicates or otherwise relates to the size, shape, and/or location ofthe attachment mechanism 814-1 in the device 800.

The visual indication 906 may also include graphical objects thatindicate information about the accessory and/or how the accessory isattached. For example, as shown in FIG. 9C, the visual indication 906includes a graphical object 912 that indicates a connection type to theaccessory. In this example, the graphical object 912 is a graphicalrepresentation of a magnet, indicating that the accessory (e.g., thecharging dock 804) has been magnetically attached via the attachmentmechanism 814-1. The same or a similar graphical object may be displayedwhen other, different accessories are attached via the attachmentmechanism 814-1.

The visual indication 906 may also include a graphical object 914 thatindicates a function of the accessory. In this example, the graphicalobject 914 is a graphical representation of a lightning bolt, indicatingthat the accessory is a charging dock or is otherwise configured tocharge the device 800. The same or a similar graphical object may bedisplayed when other accessories with charging functions are attached tothe device 800 (e.g., auxiliary battery accessories, protective caseswith built-in auxiliary batteries, etc.).

While FIGS. 9A-9C illustrate certain features in the context of anexample accessory, it will be understood that the same features mayapply to other accessories as well. For example, and as described ingreater detail herein, a wallet accessory may have a square orrectangular shape. As such, the visual indication that is displayed whenthe wallet accessory is attached may have a square or rectangulargraphical element with a same physical dimension as the wallet accessory(e.g., size, shape, width, height, etc.).

FIGS. 9A-9C illustrate an accessory being attached to the device 800,FIGS. 10A-10C illustrate the accessory being attached to the device 802.As noted above, the device 802 has a different size and/or shape thanthe device 800. For example, the device 802 is larger in length andwidth (e.g., the vertical and horizontal directions, as depicted inFIGS. 10A-10C). Further, as described above, the location of theattachment mechanism 814-2 in the device is different from the locationof the attachment mechanism 814-1 in the device 800. Accordingly, thevisual indication that is displayed when the device 802 detectsattachment of the charging dock 804 (or any other accessory) has adifferent location on the display than the visual indication shown onthe device 800. More particularly, because the location of the visualindication on a given device is based on the location of the attachmentmechanism on that device (and thus the location of the accessory, whenattached), differences in location of the attachment mechanism willresult in different locations of the visual indication.

FIG. 10A illustrates the device 802 with the representation of theattachment mechanism 814-2, as well as the charging dock 804 with itsattachment mechanism 818. The charging dock 804 also includes the cord900 that couples to a power source and provides electrical power to thecharging dock 804, and thus to the device 802 when the charging dock 804is attached to the device 802.

FIG. 10B illustrates a front view of the device 802 with the chargingdock 804 attached to the back of the device 802. As illustrated in FIG.10B, the attachment mechanism 814-2 of the device 802 and the attachmentmechanism 818 of the charging dock 804 may be coincident with oneanother, and are thus represented by a single broken circle in FIG. 10B.FIG. 10B also shows, in dotted lines, the location and physicaldimensions of the charging dock 804 and the cord 900 along the back sideof the device 802. As noted above, the attachment mechanisms 814-2, 818may be configured so that the charging dock 804 attaches to the device802 in a predetermined orientation, such as with its cord 900 extendingvertically downward (relative to the orientation of FIG. 10B). Acomparison between FIG. 9B and FIG. 10B illustrates how the differentlocation of the attachment mechanisms 814-1, 814-2 between the devices800, 802 results in the charging dock 804 being differently located onthe devices 800, 802.

The device 802 detects attachment of the charging dock 804, and inresponse to detecting the attachment of the charging dock 804, displaysa visual indication 1006 that the accessory has been attached to thedevice. The visual indication 1006 may indicate at least one property ofthe physical dimensions of the charging dock 804. For example, thevisual indication 1006 may include a graphical element 1008 that has asize and a shape that is the same as the size and the shape of thecharging dock 804. As shown in FIG. 10C, for example, the graphicalelement 1008 is a circle that has the same size and shape as thecircular charging dock 804. Further, the graphical element 1008indicates the actual location of the charging dock 804 on the device802, as indicated by the graphical element 1008 coinciding with thedotted line representing the charging dock 804 shown in FIG. 10B. Inthis manner, the visual indication 1006 may illustrate, to the user,exactly where the accessory (here, the charging dock 804) is located onthe back of the device, as well as what the size and the shape of theaccessory is, via the display on the front of the device. The visualindication 1006 may also include a fill region 1009 inside the graphicalelement 1008. In some implementations, the fill region 1009 includes anopaque element, or a translucent element, or it may be empty (e.g.,graphical objects that are displayed on the display and in the fillregion 1009 when the visual indication 1006 is displayed may be viewablethrough the fill region 1009). Further, FIG. 10C illustrates thedifferent location of the visual indication 1006 on the device 802, ascompared to the visual indication 906 on the device 800, due to thedifferent location of the attachment mechanism 814-2 in the device 802.And because the graphical element 1008 is based on the physicalcharacteristic of the accessory (e.g., size, shape, width, height,etc.), the graphical element 1008 has a same size as the graphicalelement 908.

While FIG. 10C illustrates the graphical element 1008 having the samesize and shape as the attached accessory, any physical dimensions of theaccessory may be shown by a graphical element of a visual indication.For example, the graphical element may have a same width or length asthe accessory. In some cases, the graphical element may have onephysical dimension in common with the accessory, while in other cases ithas more than one physical dimension in common. For example, thegraphical element may have the same size and shape of the accessory, orit may have the same shape (e.g., a circle), but a different size (e.g.,a different diameter). As described herein, however, the selection ofthe property of the graphical element, such as the size, shape,location, color, or the like, may be based on the particular accessorythat is attached (as determined, for example, by a near-field wirelesscommunication system).

FIG. 10C also illustrates other example graphical elements that thevisual indication 1006 may include. For example, the visual indication1006 may include a graphical element 1010 that corresponds to alocation, size, and/or shape of the attachment mechanism 814-2. Becausethe attachment mechanism 814-2 has the same size and shape as theattachment mechanism 814-1, the graphical element 1010 may have the samesize, shape, color, and/or other property as the graphical element 910in FIG. 9C. Thus, both the visual indication 906 and the visualindication 1006 may have a common element (e.g., the graphical elements910 and 1010).

The visual indication 1006 may also include graphical objects thatindicate information about the accessory and/or how the accessory isattached. For example, as shown in FIG. 10C, the visual indication 1006includes a graphical object 1012 that indicates a connection type to theaccessory. In this example, the graphical object 1012 is a graphicalrepresentation of a magnet, indicating that the accessory (e.g., thecharging dock 804) has been magnetically attached via the attachmentmechanism 814-2. The same or a similar graphical object may be displayedwhen other, different accessories are attached via the attachmentmechanism 814-2.

The visual indication 1006 may also include a graphical object 1014 thatindicates a function of the accessory. In this example, the graphicalobject 1014 is a graphical representation of a lightning bolt,indicating that the accessory is a charging dock or is otherwiseconfigured to charge the device 802. The same or a similar graphicalobject may be displayed when other accessories with charging functionsare attached to the device 802 (e.g., auxiliary battery accessories,protective cases with built-in auxiliary batteries, etc.).

While FIGS. 10A-10C illustrate certain features in the context of anexample accessory, it will be understood that the same features mayapply to other accessories as well. For example, and as described ingreater detail herein, a wallet accessory may have a substantiallysquare or rectangular shape. As such, the visual indication that isdisplayed when the wallet accessory is attached may have a substantiallysquare or rectangular graphical element with a same physical dimensionas the wallet accessory (e.g., size, shape, width, height, etc.).

As noted above, a visual indication may include a fill region, such asthe fill region 909. FIGS. 11A-11B illustrate example visual indicationswith different examples of fill regions. While FIGS. 11A-11B show thedevice 800 with the charging dock 804 attached, it will be understoodthat the fill regions described with respect to these figure appliesequally to the visual indications displayed on other devices and inresponse to the attachment of other accessories.

FIG. 11A illustrates the device 800 with the charging dock 804 attached.The device 800 is displaying a first graphical user interface 1101. Insome embodiments, the first graphical user interface 1101 is a homescreen of the device 800. The first graphical user interface 1101includes graphical objects 1104 (e.g., 1104-1, 1104-2), which mayrepresent application icons or any other graphical object of the firstgraphical user interface 1101 of the device 800.

As used herein, a home screen may refer to a graphical user interfacethat includes one or more application icons or other selectable userinterface objects that can be selected (e.g., by touching, tapping,pressing, clicking or otherwise selecting the application icon) toinitiate or launch application programs for execution by the device. Thehome screen may differ from a lock screen based on the graphical contentthat is displayed on the home screen and the lock screen. Further,whether a home screen or a lock screen is displayed may depend at leastin part on whether the device is in a locked or unlocked state. A usercan transition the device from a locked state to an unlocked state viaan authentication process (e.g., a password, a biometric authentication,or the like).

In FIG. 11A, the device 800 is also displaying a visual indication 1100,which is an embodiment of the visual indication 906, that overlies atleast a portion of the graphical user interface 1101. The visualindication 1100 includes the graphical elements 908 and 910, andgraphical objects 912 and 914. The visual indication 1100 also includesa fill region 1106. In the example of FIG. 11A, the fill region 1106 isa translucent graphical object, such that a portion of the graphicaluser interface 1101 is visible through the translucent graphical object.For example, graphical objects (or portions thereof) of the graphicaluser interface 1101 that are graphically behind or below the fill region1106, such as the graphical object 1104-2, may remain at least partiallyvisible through the fill region 1106. The fill region 1106 may have acolor and/or pattern that is visually distinct from other portions ofthe graphical user interface (e.g., outside the graphical element 908).In some cases, the color and/or pattern of the fill region 1106 is basedon a color and/or pattern of the accessory that is attached to thedevice 800. For example, if the charging dock 804 is white, the fillregion 1106 may have a white hue that matches the charging dock 804.

In FIG. 11B, the device 800 is displaying the graphical user interface1101 and a visual indication 1102, which is another embodiment of thevisual indication 906, that overlies at least a portion of the graphicaluser interface 1101. The visual indication 1102 includes the graphicalelements 908 and 910, and graphical objects 912 and 914. The visualindication 1102 also includes a fill region 1108. In the example of FIG.11B, the fill region 1108 is opaque, such that graphical objects (orportions thereof) that are graphically behind or below the fill region1108 are not displayed. Like the fill region 1106, the fill region 1108may have a color and/or pattern that is visually distinct from otherportions of the graphical user interface (e.g., outside the graphicalelement 908). In some cases, the color and/or pattern of the fill region1108 is based on a color and/or pattern of the accessory that isattached to the device 800. For example, if the charging dock 804 iswhite, the fill region 1108 may have a white hue that matches thecharging dock 804.

The visual indication that is displayed on a device in response todetecting an attachment of an accessory may include animations or othernon-static visual content. FIG. 12 illustrates one such animation inwhich a respective portion of a visual indication expands outwardly froma location that corresponds to a location of the attachment mechanism inthe device. For example, at time t₁, an accessory (e.g., the charger804) has been attached to the device 800 via the attachment mechanism814-1. In response to detecting the attachment of the accessory, thedevice 800 displays a visual indication 1201 that includes a boundary1200. The boundary 1200 originates at a location that corresponds to theattachment mechanism 814-1, such as a center of the attachment mechanism814-1. The boundary 1200 encloses a fill region 1202, and expands orradiates outward from its origin, as indicated by arrows 1204.

As the animation continues, shown at t₂, the boundary 1200 has expanded(past the location of the attachment mechanism 814-1, and continues toexpand until it reaches the size and shape of the charging dock 804 (orany other suitable accessory, such as a wallet accessory, auxiliarybattery accessory, or the like). At time t₃, the boundary 1200 and fillregion 1202 have expanded to their full and final size and shape, whichcoincides with the size and shape of the attached accessory. Theresulting visual indication 1201 includes the boundary 1200 and the fillregion 1202, which may be the same as or similar to the graphicalelement 908 and the fill region 909 of FIG. 9C, as well as the graphicalelements 908 and 910, and graphical objects 912 and 914. The fill region1202 may be translucent or opaque, as described above with respect toFIGS. 11A-11B.

FIG. 12 shows the example animation of the visual indication withreference to a visual indication that is displayed in response to theattachment of a charging dock. A similar animation may be displayed,however, with visual indications that are displayed in response to theattachment of different accessories. In such cases, the particularshapes, sizes, colors, and/or other properties of the portions that areanimated (e.g., expand outwardly) may correspond to (e.g., match) theshapes, sizes, colors, and/or other properties of the attachedaccessories. For example, a rectangular wallet accessory may cause arectangular boundary to expand (e.g., radiate) outwardly from a locationof the attachment mechanism 814-1, until it reaches the size and shapeof the wallet accessory. While FIG. 12 shows dotted lines representingthe attachment mechanism 814-1 and the outer boundary of the chargingdock 804, these are provided for reference and are not included asgraphical objects of the visual indication 906.

FIGS. 13A-13C illustrate another example accessory being attached to thedevice 800. In particular, FIGS. 13A-13C illustrate the auxiliarybattery accessory 808 being attached to the device 800. FIG. 13Aillustrates the device 800 with the representation of the attachmentmechanism 814-1, as well as the auxiliary battery accessory 808 with itsattachment mechanism 818. In some implementations, the auxiliary batteryaccessory 808 includes a battery and a wireless charging system tofacilitate wireless charging of the device 800 by the battery accessory808.

FIG. 13B illustrates a front view of the device 800 with the auxiliarybattery accessory 808 attached to the back of the device 800. Asillustrated in FIG. 10B, the attachment mechanism 814-1 of the device800 and the attachment mechanism 818 of the auxiliary battery accessory808 may be coincident with one another, and are thus represented by asingle broken circle in FIG. 13B. FIG. 13B also shows, in dotted lines,the location and physical dimensions of the auxiliary battery accessory808 along the back side of the device 800. As noted above, theattachment mechanisms 814-1, 818 may be configured so that the auxiliarybattery accessory 808 attaches to the device 800 in a predeterminedorientation, such as with its sides (e.g., top, bottom, left, and rightsides) parallel to the sides (e.g., top, bottom, left, and right sides)of the device 800. While the instant figures show dotted linesrepresenting the attachment mechanisms 814-1 and 818, these are providedfor reference and are not included as graphical objects of the visualindication 906.

The device 800 detects attachment of the auxiliary battery accessory808, and in response to detecting the attachment of the auxiliarybattery accessory 808, displays a visual indication 1300 that theaccessory has been attached to the device. The visual indication 1300may indicate at least one property of the physical dimensions of theauxiliary battery accessory 808. For example, the visual indication 1300may include a graphical element 1308 that has a size and a shape that isthe same as the size and the shape of the auxiliary battery accessory808. As shown in FIG. 13C, for example, the graphical element 1308 is asquare (or substantially rectangular shape) that has the same size andshape (or approximately the same size and shape) as the square auxiliarybattery accessory 808. Further, the graphical element 1308 indicates theactual location of the auxiliary battery accessory 808 on the device800, as indicated by the graphical element 1308 coinciding with theborder of the auxiliary battery accessory 808 shown in broken lines inFIG. 13B. In this manner, the visual indication 1300 may illustrate, tothe user, exactly where the accessory (here, the auxiliary batteryaccessory 808) is located on the back of the device, as well as what thesize and the shape of the accessory is, via the display on the front ofthe device. The visual indication 1300 may also include a fill region1309 inside the graphical element 1308. In some implementations, thefill region 1309 includes an opaque element, or a translucent element,or it may be empty (e.g., graphical objects that are displayed on thedisplay and in the fill region 1309 when the visual indication 1300 isdisplayed may be viewable through the fill region 1309).

FIG. 13C also illustrates other example graphical elements and/orgraphical objects that the visual indication 1300 may include. Forexample, as shown in FIG. 13C the visual indication 1300 includes agraphical element 1310 that corresponds to a location, size, and/orshape of the attachment mechanism 814-1 (e.g., a ring or circle that iscoincident with the location of the attachment mechanism 814-1). Thevisual indication 1300 also includes graphical objects that indicateinformation about the accessory and/or how the accessory is attached.For example, the visual indication 1300 includes a graphical object 1312that indicates a connection type to the accessory (e.g., a magnet,indicating that the accessory has been magnetically attached), and agraphical object 1014 that indicates a function of the accessory (e.g.,a graphical representation of a lightning bolt, indicating the thataccessory is configured to charge the device 800).

As described herein, different visual indications associated withdifferent accessories may have common elements. For example, the visualindication 906 (FIG. 9C) and the visual indication 1300 (FIG. 13C) bothinclude a common graphical element (e.g., the graphical elements 910,1310) displayed at a location that corresponds to a location of theattachment mechanism 814-1. This common graphical element indicates thatthe accessories, though they are different accessories, both attach tothe device 800 using the same attachment mechanism. Other similaritiesbetween accessories may also be indicated by other common graphicalelements and/or graphical objects in the visual indications. Forexample, the charging dock 804 and the auxiliary battery accessory 808both attach to the device 800 magnetically, and both provide power tocharge the device 800. Accordingly, the visual indication 906 (FIG. 9C)and the visual indication 1300 (FIG. 13C) both include a commongraphical object indicating the magnetic attachment technique (themagnet graphic 912, 1312) and a common graphical object indicating thecharging functionality (the lightning bolt 914, 1314). Of course, themagnet and lightning bolt are merely examples, and other graphicalelements and/or objects may be used instead of or in place of the magnetand lightning bolt.

FIG. 13C also illustrates how the different physical properties ofdifferent accessories result in visual indications that have differentproperties. For example, the auxiliary battery accessory 808 (attachedto the device 800 in FIG. 13C) has a first shape (e.g., square), and thecharging dock 804 (attached to the device 800 in FIG. 9C) has a secondshape that is different from the first shape (e.g., circular).Accordingly, the visual indication 1300 has a graphical element 1308having the first shape (e.g., square), and the visual indication 906 hasa graphical element 908 having the second shape (e.g., circular). Insome implementations, a similar result occurs when the accessories havedifferent sizes. For example, if the first accessory has a first sizeand the second accessory has a second size, the first visual indicationhas the first size and the second visual indication has the second size.With reference to the visual indications 906 and 1300, for example, theauxiliary battery accessory 808 is shorter (e.g., in a verticaldirection) than the charging dock 804. Accordingly, the visualindication 1300 has a graphical element 1308 that is shorter (e.g., inthe vertical direction) than the graphical element 908 of the visualindication 906.

FIGS. 14A-14B illustrate another example accessory being attached to thedevice 800. In particular, FIGS. 14A-14B illustrate the protective case810 being attached to the device 800. FIG. 14A illustrates the device800 with the representation of the attachment mechanism 814-1, as wellas the protective case 810 with its attachment mechanism 818. In someimplementations, the protective case 810 lacks an attachment mechanism.In such cases, the protective case 810 may include other retention orcoupling features to retain the protective case 810 to the device 800(e.g., clips, flanges, fasteners, etc.). Whether or not the protectivecase 810 includes an attachment mechanism 818, the protective case 810includes a near-field wireless communication antenna or othercomponent(s) that facilitate detection, by the device 800, of theprotective case 810 being attached to the device 800.

The device 800 detects attachment of the protective case 810, and inresponse to detecting the attachment of the protective case 810,displays a visual indication 1400 that the accessory has been attachedto the device. The visual indication 1400 may indicate at least oneproperty of the protective case 810. For example, the visual indication1400 may include a graphical element 1408 (e.g., a border) displayed atthe outermost area of the display of the device 800, indicating that theprotective case 810 completely covers the back of the device 800. Thevisual indication 1400 may also include a fill region 1409 inside thegraphical element 1408. In some implementations, the fill region 1409includes an opaque element, or a translucent element, or it may be empty(e.g., graphical objects that are displayed on the display and in thefill region 1409 when the visual indication 1400 is displayed may beviewable through the fill region 1409). In some implementations, thefill region 1409 has a color that matches or is based on a color of theprotective case 810. In some implementations, the visual indication 1400is displayed as part of a color effect in which a wash of color sweepsacross the display of the device when the protective case 810 isattached to the device 800. The color (e.g., corresponding to the fillregion 1409) may sweep across the display as shown in FIG. 3C, resultingin an at least temporary display of the fill region 1409 occupying allor substantially all of the display. In some implementations, the visualindication 1400 omits the graphical element 1408, and the fill region1409 is borderless. In some implementations, the color wash effectincludes an animation in which the color expands outward from a locationcorresponding to the attachment mechanism 814-1.

In some implementations, multiple accessories may be used togethersimultaneously with a single device. For example, both a protective case(e.g., the protective case 810) and an additional accessory, such as anauxiliary battery accessory, wallet accessory, charging dock, or thelike, may be attached to a device. In such cases, each accessory maytrigger the display of a visual indication that indicates the attachmentof the accessory to the device, even if another accessory is alreadyattached to the device. FIGS. 15A-15B illustrate an example in anadditional accessory (e.g., the charging dock 804) is attached to thedevice 800 while the device 800 has the case 810 attached. FIG. 15Ashows the device 800 prior to attachment of the charging dock 804. FIG.15B shows the device 800 after attachment of the charging dock 804. Inparticular, the device 800 detects attachment of the additionalaccessory (e.g., the charging dock 804), and, in response to detectingthe attachment of the additional accessory, the device 800 displays avisual indication indicating that the additional accessory has beenattached to the device, where the visual indication indicates at leastone property of the physical dimensions of the additional accessory. Thevisual indication shown in FIG. 15B is the visual indication 906,because the accessory is the charging dock 804. Accordingly, the visualindication 906 indicates a physical dimension of the charging dock 804,as described above with respect to FIGS. 9A-9C.

FIGS. 14A-15B also illustrate how different accessories having differentphysical dimensions cause visual indications having different physicaldimensions to be displayed. For example, the visual indication 1400 inFIG. 14B occupies the entire area of the display, while the visualindication 906 occupies less than an entire area of the display.

Visual indications that are displayed in response to detectingattachment of an accessory may also include information associated withthe accessory. In some implementations, the visual indications includetext that indicates a name of the owner of the accessory, a state ofcharge of the accessory (e.g., if the accessory includes a battery, suchas in the case of an auxiliary battery accessory), a room or locationassociated with the accessory (e.g., if the accessory is a dock or otheraccessory that is located in a bedroom, kitchen, living room, or thelike). FIGS. 16A-16B illustrates example visual indications that includeinformation associated with an accessory.

FIG. 16A, for example, shows the device 800 displaying a visualindication 1600 after the auxiliary battery charging accessory 808 isattached to the device 800. The visual indication 1600 includesinformation 1602 and 1603 associated with the accessory. In particular,as shown in FIG. 16A, the information 1602 includes a name of theaccessory's owner (e.g., “User 1's Battery Accessory”), and theinformation 1603 includes a state of charge of the accessory (e.g., “65%Charged”). FIG. 16B shows the device 800 displaying a visual indication1604 after a different accessory (e.g., the wallet accessory 806) isattached to the device 800. The visual indication 1604 includesinformation 1606 associated with the accessory. In particular, as shownin FIG. 16B, the information 1606 includes a name of the accessory'sowner (e.g., “User 2's Wallet”). Other types of information associatedwith an accessory may be displayed, and different accessories may causedifferent information to be displayed. For example, a user may be ableto assign names to accessories to help personalize the accessories andpersonalize the visual indications that are displayed upon detection ofthe attachment of the accessory.

In some cases, devices also produce outputs in response to detachment ofan accessory. For example, as noted above with respect to FIG. 3P, inresponse to detecting detachment of a wallet accessory from the device,the device may display a map with a graphical indicator representing thelocation where the wallet accessory was detached. In someimplementations, instead of or in addition to displaying a visualindication such as a map, a device may produce a non-visual output, suchas a tactile output and/or an audio output.

FIGS. 17A-17B illustrate example detach outputs that may be produced inresponse to attachment and detachment of an accessory and a device.Detach outputs indicate that the accessory has been detached from thedevice. In some implementations, detach outputs include tactile outputs,such as vibrations, and/or audio outputs, such as beeps or tones. Insome implementations, detach outputs include visual indications, such asa textual alert and/or a map showing a detachment location.

As shown in FIG. 17A, when an accessory, such as the wallet accessory806, is attached to the device 800, the device detects attachment of theaccessory. In some implementations, in response to the detection, thedevice 800 displays a visual indication 1700. The visual indication 1700may include a portion (e.g., the border 1702) that expands outward (asindicated by arrows 1704) from a location that corresponds to theattachment mechanism. As described above, the border 1702 may expandoutward until it reaches the border 1705 that corresponds to the sizeand shape of the wallet accessory, as indicated by the broken-lineborder 1705.

FIG. 17B illustrates operation of the device 800 in response todetecting detachment of the wallet accessory 806. The device 800 detectsdetachment of the accessory, which may be intentional or accidental,from the device 800. In some implementations, in response to detectingthe detachment, the device 800 produces a detach output indicating thatthe accessory has been detached from the device. In someimplementations, generating the detach output includes generating anon-visual output, such as a tactile output and/or audio outputindicating detachment of the accessory.

In some implementations, the device 800 produces a detach output inresponse to detachment of some accessories, but not in response todetachment of other accessories. For example, in response to detectingthe detachment of an accessory, in accordance with a determination thatthe accessory is a first type of accessory, the device 800 generates adetach output, and in accordance with a determination that the accessoryis a second type of accessory, the device 800 foregoes generation of thedetach output. In some implementations, generating the detach outputincludes generating a tactile output 1708 and/or audio output 1706indicating detachment of the accessory. In some implementations,forgoing generation of the detach output includes foregoing generationof a tactile output 1708 and/or audio output 1706 indicating detachmentof the accessory.

In some implementations, the tactile output 1708 is a vibration,impulse, or the like. In some implementations, the audio output 1706 isa beep, tone, melody, song, voice alert, or the like. In someimplementations, a detach output includes both tactile and audiooutputs. In some implementations, the detach output includes anon-visual output (e.g., the tactile output and/or audio output) and/ora visual indication.

In some implementations, the tactile output and/or audio output includedin the detach output is the same as a tactile output and/or audio outputthat is generated when the accessory is attached. In someimplementations, the tactile output and/or audio output in the detachoutput is different from a tactile output and/or audio output that isgenerated when the accessory is attached. In some implementations, thetactile output and/or audio output in the detach output includes acomponent of the tactile output and/or audio output that is generatedwhen the accessory is attached and includes a component that isdifferent from the tactile output and/or audio output that is generatedwhen the accessory is attached. For example, in some implementations,the audio output that is generated when the accessory is attached is thesame as the audio output that is generated when the accessory isdetached, and the tactile output that is generated when the accessory isattached is the same as the tactile output that is generated when theaccessory is detached. In some implementations, the audio output that isgenerated when the accessory is attached is different from the audiooutput that is generated when the accessory is detached, and the tactileoutput that is generated when the accessory is attached is the same asthe tactile output that is generated when the accessory is detached. Insome implementations, the audio output that is generated when theaccessory is attached is the same as the audio output that is generatedwhen the accessory is detached, and the tactile output that is generatedwhen the accessory is attached is different than the tactile output thatis generated when the accessory is detached. In some implementations,the audio output that is generated when the accessory is attached isdifferent than the audio output that is generated when the accessory isdetached, and the tactile output that is generated when the accessory isattached is different than the tactile output that is generated when theaccessory is detached.

As noted above, whether or not a detach output is produced may depend onthe type of accessory that is detached. In some implementations, thedetach output is produced if the detached accessory is a walletaccessory, and is not produced if the detached accessory is a chargingdock, protective case, or auxiliary battery accessory. In someimplementations, whether a non-visual output is produced when aparticular type of accessory is detached is based on a user preference(e.g., the user can select particular accessories and/or particulartypes of accessories that will produce non-visual outputs upon theirdetachment). In some implementations, whether a non-visual output isproduced when a particular type of accessory is detached is based on apredetermined setting based on the accessory type. In someimplementations, accessories that include or may contain personallyidentifiable information about a user, such as a wallet accessory,produce non-visual outputs when detached, while other accessories, suchas auxiliary battery accessories, do not.

In some implementations, a detach output includes a visual detachindication. In some implementations, the visual detach indicationincludes a map showing a location at the time of detachment. In someimplementations, the visual detach indication includes textualinformation about the detached accessory and/or the detachment event. Insome implementations, the visual detach indication includes a graphic.

In some implementations, the visual detach indication appears to be theopposite of a visual indication that is displayed in response todetection of the attachment of the accessory. For example, in someimplementations, the first visual indication (e.g., the visualindication that is displayed in accordance with a determination that anattached accessory is a first accessory) is an animated visualindication, and the second visual indication (e.g., the visualindication that is displayed in accordance with a determination that anattached accessory is a second accessory) is an animated visualindication, and displaying the visual detach indication includes, inaccordance with a determination that the accessory is the firstaccessory, displaying a third visual indication that includes a reversalof at least a portion of (or all of) the first visual indication, and inaccordance with a determination that the accessory is the secondaccessory, displaying a fourth visual indication that is different fromthe third visual indication and that includes a reversal of at least aportion of (or all of) the second visual indication. The fourth visualindication may be different than the third visual indication in size,color, content, or the like. For example, the first accessory may besmaller than the second accessory, and as such the third visualindication (e.g., the visual detach indication for the first accessory)may be smaller than the fourth visual indication (e.g., the visualdetach indication for the second accessory).

FIG. 17B illustrates an example visual detach indication 1710 that maybe displayed in response to detecting detachment of an accessory. Inthis example, the visual detach indication 1710 includes a graphicalelement 1712 (e.g., a border or boundary) that coincides with the size,shape, and/or position of the wallet accessory 806 on the back of thedevice 800. The visual detach indication 1710 may also include ananimation in which the graphical element 1712 retracts inward (asindicated by the arrows 1714) to a location 1713 that corresponds to theattachment mechanism 814-1. The retracting animation of the visualdetach indication 1710 that is displayed in response to detectingdetachment may appear to be the opposite to the expanding animation ofthe visual indication 1700 that is displayed in response to detectingattachment of the accessory. Like the non-visual outputs describedabove, in some implementations the visual detach indication 1710 isproduced in accordance with a determination that the accessory is afirst accessory, and is not produced in accordance with a determinationthat the detached accessory is a second accessory. For example, in somecases the visual detach indication 1710 is produced if the detachedaccessory is a wallet accessory, and is not produced if the detachedaccessory is a charging dock, protective case, or auxiliary batteryaccessory.

Whether or not the visual detach indication 1710 is displayed may dependon a status of the device 800 when the detachment is detected. Forexample, in some implementations, if the device 800 is displaying a lockscreen (or an application graphical user interface), the visual detachindication 1710 is shown in response to detecting detachment of theaccessory, and if the device 800 is displaying a home screen, the visualdetach indication 1710 is not shown in response to detecting detachmentof the accessory.

The visual detach indication 1710 shown in FIG. 17B is one examplevisual detach indication that may be displayed in response to detectingthat an accessory has been detached. In some implementations, the visualdetach indication 1710 includes a map (e.g., the map 373 in FIG. 3P). Insome implementations, the visual detach indication is displayed until itis acknowledged by the user (e.g., by the user selecting a selectableuser interface object), or for a duration (e.g., 10 seconds, 20 seconds,or the like).

As noted in several examples above, whether or not a particular visualindication is displayed in response to detection of an attachment ordetachment of an accessory may be based at least in part on a state ofthe device, such as what the display is displaying at the time ofdetection (e.g., a lock screen, a home screen, an application graphicaluser interface), a lock state of the device at the time of thedetection, or the like. FIGS. 18A-18B illustrate examples of howdifferent device states may result in different visual indications beingdisplayed in response to detecting attachment of an accessory. WhileFIGS. 18A-18B relate to visual indications shown in response todetecting an attachment of a particular accessory (e.g., the chargingdock 804), the same concepts apply to visual detach indications (as wellas non-visual indications) that are displayed or otherwise produced inresponse to detecting a detachment of other accessories (e.g., thewallet accessory, the auxiliary battery accessory, a protective case,etc.).

FIG. 18A illustrates the device 800 in a first state. In the example ofFIG. 18A, the first state corresponds to the device 800 being locked anddisplaying a lock screen 1800, though this is merely one example. Inother examples, the first state corresponds to a different device state,such as the device displaying being locked but not displaying anything,the device displaying a home screen, or the like.

A lock screen, such as the lock screen 1800, may be displayed when thedevice is locked, the user has not been authenticated, and/or the userhas not provided a password, passcode, or otherwise authorized theunlocking of the device. In some implementations, the lock screen 1800does not include application icons, or includes a limited set ofapplication icons (e.g., those that have been selected by the user). Insome implementations, device functions and/or data that are availablevia the lock screen (e.g., in response to a user selection of anapplication icon or other selectable user interface object) may belimited (e.g., personally identifiable information or applications thatmay access personally identifiable information may be inaccessible).

In some implementations, in accordance with a determination that thedevice 800 is in the first state (e.g., displaying the lock screen 1800)when the attachment of the accessory is detected, the device 800displays the first visual indication in accordance with a determinationthat the accessory is the first accessory. For example, as shown in FIG.18A, the device 800 determines that the attached device is the chargingdock 804 (on the back of the device 800) and displays a visualindication 1802 (which corresponds to the visual indication 1006associated with the charging dock 804). The device 800 may also displaya second visual indication in accordance with a determination that theaccessory is a second accessory. Thus, for example, if the accessorywere the wallet accessory 806 instead of the charging dock 804, thedevice 800 would display a different visual indication (e.g., the visualindication 1604, FIG. 16B).

In some implementations, in accordance with a determination that thedevice is in a second state, different from the first state, when theattachment of the accessory is detected, the device 800 forgoes displayof the first visual indication and/or the second visual indication. Forexample, FIG. 18B illustrates the device 800 in an example second state,in which the device 800 is displaying a home screen 1804. In otherexamples, the second state corresponds to the device 800 displaying anapplication graphical user interface. As described above, the homescreen 1804 may include one or more application icons (selectable userinterface objects), which, when selected, initiates an applicationand/or causes the device to display an application graphical userinterface. When the charging dock 804 (or other example accessory) isattached to the device 800 when the device 800 is in the second state,the device 800 may forego display of the visual indication that isdisplayed when the charging dock 804 is attached when the device is inthe first state.

In some implementations, a different visual indication is provided inresponse to the device 800 detecting attachment of the accessory whenthe device 800 is in the second state. The different visual indicationmay be different than the visual indication that is displayed when thedevice 800 is in the first state and detects attachment of the sameaccessory. For example, FIG. 18B illustrates a visual indication 1806that is optionally displayed by the device 800 in response to the device800 detecting attachment of the charging dock 804 when the device 800 isin the second state. In some implementations, the visual indication 1806is smaller than the visual indication 1802. In some implementations, theoptional visual indication 1806 is displayed in a border region of thedisplay that includes system status information, a graphicalrepresentation of a current time, battery charge status, or the like.

As described above with respect to FIG. 3D-3F, a device may change fromdisplaying a first graphical user interface to a second graphical userinterface in response to the device being used with a case thatpartially covers the display of the device, but which has an opening orwindow through which part of the display remains visible. FIGS. 19A-20Billustrate examples of how devices may transition between differentgraphical user interfaces when the devices detect that they have beeninserted in or otherwise attached to cases that define openings thatallow limited viewing of the device display. For example, when usedwithout the protective case, a device may display graphical content inan entire display area, and when used with the protective case, displaygraphical content in only a portion of the display area. As describedherein with respect to FIGS. 21A-21B, the limited area that is viewablethrough the window of a protective case may be referred to as a secondregion of the display, while an area outside the second region (e.g.,which is covered by the protective case) may be referred to as a firstregion of the display. In some implementations, the first region and thesecond region together define the entire display area.

With reference to FIG. 19A, in some implementations a device, such asthe device 800, displays a first graphical user interface 1904. In theexample shown in FIG. 19A, the first graphical user interface 1904 is ahome screen that includes selectable user interface objects (e.g.,application icons) displayed in a first region of the display and in thesecond region of the display (as described in greater detail withrespect to FIGS. 21A-21B).

In some implementations, the first graphical user interface 1904includes first graphical content displayed in a first region of thedisplay, and second graphical content displayed in a second region ofthe display, where the second region is different than the first region.FIG. 21A illustrates the first and second regions of the display. Forexample, the first region 2101 corresponds to the area outside theborder 2102 (e.g., the border of the opening 1902 in the protective case1900), and the second region 2100 corresponds to the area inside theborder 2102. As shown in FIG. 19A, the first region of the display iscovered by the case 1900, and the second region of the display isvisible through an opening 1902 in the case 1900 (e.g., in a wall of thecase 1900 that covers at least part of the display of the device 800).

Once the device 800 is coupled to the case 1900 (e.g., by inserting thedevice 800 into an opening of the case 1900), the device 800 detects thecoupling of the case 1900 to the device 800. In some implementations,detection is performed using a near-field wireless communication systemof the device 800 and a near-field wireless communication antenna of thecase 1900.

In response to detecting the coupling of the case 1900 to the device800, the device 800 transitions from displaying the first graphical userinterface 1904 to displaying a second graphical user interface 1905,where the transitioning includes ceasing to display the second graphicalcontent in the second region of the display (e.g., ceasing to displayapplication icons or other graphical content in the area of the displaycorresponding to the opening 1092), and displaying a second graphicaluser interface 1905 on the display. The second graphical user interface1905 includes third graphical content, different from the secondgraphical content, displayed in the second region of the display. Forexample, the second graphical user interface 1905 includes graphicalcontent in the opening 1902 that is different than what was displayed bythe first graphical user interface.

In some implementations, the transition from the first graphical userinterface 1904 to the second graphical user interface 1907 furtherincludes, prior to displaying the second graphical user interface,displaying a black background graphic in the second region of thedisplay. The black background may be displayed for a predetermined timeprior to displaying the second graphical user interface 1907 (e.g., 1second, 2 seconds, 3 seconds, etc.).

The second graphical user interface 1905 includes different content inthe second region (e.g., the second region 2100, FIG. 21A) than what wasthe first graphical user interface 1904. For example, as shown in FIG.19B, first graphical user interface 1904 includes selectable userinterface objects, while the second graphical user interface 1905includes a background graphic 1906 and a foreground graphic 1907. Insome implementations, the background graphic 1906 is an image, a color,a pattern, or the like. In some implementations, the foreground graphic1907 is a graphical representation of a current time (e.g., a digital oranalog clock), though other foreground graphics 1907 are also possible,and may include notifications, device status information, animations,selectable user interface objects (also referred to as affordances), orthe like.

In some implementations, the background graphic 1906 has a first colorthat matches a color of the case 1900. For example, if the case 1900 isyellow, the background graphic 1906 may also be yellow. In someimplementations, the foreground graphic 1907 has a second color that isdifferent than the first color (e.g., different than the color of thecase 1900).

In some implementations, the background graphic 1906 initially (e.g.,when the background 1907 is first displayed in response to detection ofthe coupling of the case 1900) has a first color that matches a color ofthe case 1900, and the foreground graphic 1907 initially (e.g., when thebackground 1906 is first displayed in response to detection of thecoupling of the case 1900) has a second color different from the firstcolor. In some implementations, after the background graphic having thefirst color and the foreground graphic having the second color aredisplayed, the device 800 transitions the background graphic from thefirst color to a third color. Thus, for example, if the case 1900 isblue, the background graphic 1906 may initially be blue, and then it maytransition to a different color (e.g., black).

In some implementations, after the background graphic 1906 having thefirst color (e.g., the color of the case 1900) and the foregroundgraphic 1907 having the second color are displayed, the device 800transitions the foreground graphic 1907 from the second color to thefirst color. Thus, for example, the background graphic 1906 may start asthe color of the case, and then transition to a different color (e.g.,black), and the foreground graphic 1907 may start as a different colorthan the case (e.g., black), and then transition to the color of thecase. In some implementations, the transition of the foreground graphic1907 to the first color (e.g., the color of the case 1900) occurssimultaneously with the transition of the background graphic 1906. Inother implementations, it occurs before or after the transition of thebackground graphic 1906.

If the case 1900 has multiple colors, the background and/or foregroundgraphics 1906. 1907 may incorporate the multiple colors of the case. Forexample, for a case having at least a first and a second color, in someimplementations the background graphic 1906 has the first color of thecase (e.g. a primary color of the case), and the foreground graphic 1907has the second color of the case (e.g., a secondary color of the case).In some implementations, the background graphic 1906 initially has thefirst color of the case, and transitions from the first color to thesecond color after a predetermined time. In the latter case, theforeground graphic 1907 may remain the same color during the transitionof the background graphic 1906 (e.g., a different color than the firstand second colors than the case), or may transition between differentcolors. For example, in some implementations the background graphic 1906transitions from the first color of the case to the second color of thecase, and the foreground graphic 1907 is initially the second color ofthe case and transitions to the first color of the case.

FIG. 19A depicts the device 800 being coupled to a protective case 1900,and example changes to what the device 800 displays in response to beingcoupled to the case 1900. FIG. 19B depicts the device 802, which is hasdifferent dimensions than the device 800 (e.g., the device 802 is largerthan the device 800) being coupled to a protective case 1910. Further,the opening 1912 in the case 1910 (e.g., in a wall of the case thatcovers at least part of the display of the device 800) has a differentlocation than the opening 1902 of the case 1900. For example the opening1902 of the case 1900 is positioned a first distance 1908 from a top ofthe case 1900, while the opening 1912 of the case 1910 is positioned asecond distance 1918 (different from the first distance) from the top ofthe case 1910. FIG. 19B illustrates that while the device 802 may takethe same or similar actions as the device 800 upon detecting thecoupling to the case, the locations of the graphical content that isbeing displayed may differ based on the different size of the device 802and the different location of the opening 1912 in the case 1910.

In particular, FIG. 19B shows the device 802 displaying a firstgraphical user interface 1914, which may be a home screen that includesselectable user interface objects, similar to the first graphical userinterface 1904 in FIG. 19A. In response to detecting that it is coupledto the case 1910, the device 802 transitions from displaying the firstgraphical user interface 1914 to displaying a second graphical userinterface 1915. Like the second graphical user interface 1905, thesecond graphical user interface 1915, in some implementations, includesa background graphic 1916 and a foreground graphic 1917. The sametransition operations described above with respect to FIG. 19A applyequally to the device and graphical user interfaces in FIG. 19B.

FIGS. 20A-20B illustrate additional examples of how a device may reactin response to detecting that it has been coupled to a protective case.FIGS. 20A-20B illustrate the examples using the device 802 and the case1910, though it will be understood that the examples apply equally tothe device 800 and case 1900.

FIG. 20A illustrates the device 802 displaying a blank display 2000. Theblank display may correspond to the display being inactive and/or off.In response to detecting that it is coupled to the case 1910, the device802 transitions from the blank display 2000 (e.g., displaying nographical content) to displaying the second graphical user interface1915.

FIG. 20B illustrates the device 802 displaying a first graphical userinterface that is a lock screen 2002. In some implementations, the lockscreen 2002 includes a first graphical object 2008 (in this case, alocked padlock indicating the locked status of the device), and a secondgraphical object 2004 (in this case, a digital clock). In response todetecting that it is coupled to the case 1910, the device 802transitions from the first graphical user interface (e.g., the lockscreen 2002) to displaying the second graphical user interface 1915. Asillustrated in FIG. 20B, the transition includes ceasing to display thesecond graphical object 2004 in a first location (e.g., its location inthe lock screen 2002), and displaying the second graphical object 2004in the second graphical user interface 1915.

As described above, FIGS. 21A-21B illustrate examples of the differentregions of the displays of the devices 800, 802, and how the regionsrelate to the graphical content of the graphical user interfaces and thepositions of the openings in the protective cases. FIG. 21A shows thedevice 800, and a boundary 2102 that corresponds to the opening 1902 ofthe protective case 1900. The boundary 2102 may define the first andsecond regions of the display. For example, as shown, the first region2101 is outside the boundary 2102, and the second region 2100 is insidethe boundary 2102. FIG. 21A also shows example locations of graphicalobjects of the graphical user interface. For example, selectable userinterface objects (e.g., the application icon 2104) of a home screengraphical user interface may be displayed both in the first region 2101and the second region 2100, and some may span both the first and thesecond regions. As described above, in response to detecting that thedevice 800 is coupled to the case 1900, the device 800 ceases to displaythe graphical content in the second region 2100 (e.g., the applicationicons 2104 that are fully or partially within the second region 2100),and instead displays other graphical content of a different graphicaluser interface.

Similarly, FIG. 21B shows the device 802, and a boundary 2106 thatcorresponds to the opening 1912 of the protective case 1920. Theboundary 2106 may define the first and second regions of the display.For example, as shown, the first region 2107 is outside the boundary2106, and the second region 2105 is inside the boundary 2106. FIG. 21Balso shows example locations of graphical objects of the graphical userinterface. For example, selectable user interface objects (e.g., theapplication icon 2108) of a home screen graphical user interface may bedisplayed both in the first region 2107 and the second region 2105, andsome may span both the first and the second regions. As described above,in response to detecting that the device 810 is coupled to the case1910, the device 802 ceases to display the graphical content in thesecond region 2105 (e.g., the application icons 2108 that are fully orpartially within the second region 2105), and instead displays othergraphical content of a different graphical user interface.

FIGS. 21A-21B also illustrate how the location of the openings of theprotective cases 1900 and 1910 differ, therefore resulting in differentrelative locations of the first and second regions on the differentdevices 800, 802. Thus, the particular locations where the secondgraphical user interface is displayed on a given device can depend onthe location of the opening in a case. In some implementations, thelocation of the opening of a case (and thus the particular locations ofthe first and second regions) is detected by the device via near-fieldwireless communication with the case. For example, the device mayreceive from the case, and via the near-field wireless communicationsystem, the location of the opening, and, upon detecting the coupling tothe case, display the second graphical user interface in a region of thedisplay that corresponds to the location of the opening.

FIGS. 19A-20B illustrate a second graphical user interface that isdisplayed in a second region of a display (e.g., a region correspondingto an opening in a protective case), in accordance with someimplementations. FIG. 22 illustrates another example second graphicaluser interface 2200 that may be displayed in the second region of adisplay. FIG. 22 illustrates the second graphical user interface 2200 inconjunction with the case 1910 (and thus the device 802), though thesame or similar second graphical user interface may be used inconjunction with the case 1900 and the device 800 (and/or otherimplementations of a device and case in accordance with the instantapplication).

In some implementations, the second graphical user interface 2200includes graphical objects such as graphical objects 2202, 2204, and2204. The graphical object 2202 is a weather object (e.g., indicatingcurrent and/or predicted weather conditions for a geographic area, whichmay be user-selected or based on the geographic location of the device).The graphical object 2204 is a clock object (e.g., indicating thecurrent time). The graphical object 2206 is a date object (e.g.,indicating the current day, date, and month, and optionally year). Thegraphical objects 2202, 2204, 2206 may be selectable user interfaceobjects that, when selected by a user (e.g., by touching, tapping,pressing, clicking, and/or otherwise selecting the graphical objects)causes additional information related to the graphical object to bedisplayed (e.g., a user selection of the graphical object 2202 may causea multi-day weather forecast to be displayed in the second region of thedisplay).

The graphical content that is displayed in the second region of thedisplay (and thus is viewable in the opening in a protective case) maychange as a result of various events and/or actions. For example, insome implementations, while the case is coupled to the device, thedevice detects an occurrence of an event, and in response to detectingthe occurrence of the event, displays, in the second region of thedisplay, a graphical object associated with the event. In someimplementations, the graphical object is a selectable user interfaceobject, also referred to as an affordance, that, when selected by a user(e.g., by touching, tapping, pressing, clicking, or otherwise selectingthe graphical object), causes the device to perform an action oroperation.

FIG. 23 illustrates various examples of graphical objects that may bedisplayed in a second region 2302 of a display in response to the devicedetecting the occurrence of an event. In each example, the second region2302 (e.g., corresponding to the second region 2100 or 2105) is showninitially displaying the second graphical user interface 2300 (e.g., thesecond graphical user interface 1905), though this is only one examplestate of the second region 2302 prior to detecting the occurrence of anevent. In other cases, the second region 2302 is blank, and in yet othercases the second region 2302 may be displaying a different graphicaluser interface. Further, in each example, the transition from displayingthe second graphical user interface to displaying a graphical objectoccurs in response to detecting the occurrence of the event.

In example 2301, the event is a notification of a received message. Insome implementations, the received message is a text message, an SMSmessage, an email, a message from an internet messaging application, orthe like. In some implementations, in response to detecting thenotification of the received message, the device displays, in the secondregion 2302, a message notification object 2304 (e.g., a first graphicalobject), and message information 2306 (e.g., a second graphical object).In some implementations, the message information 2306 includes anindication of the type of message (e.g., text message, email, etc.), anda name of a sender of the message.

In some implementations, one or both of the message notification object2304 and the message information 2306 are affordances (e.g., selectableuser interface objects) that, when selected by a user (e.g., bytouching, tapping, pressing, clicking, and/or otherwise selecting thegraphical objects) cause the device to perform an additional actionrelated to the event. For example, in some implementations, selectingthe message notification object 2304 or the message information 2306causes at least a portion of the message to be displayed in the secondregion 2302 of the display.

In example 2303, the event is a notification of an incoming call (e.g.,a voice call, a video call, or the like). In some implementations, inresponse to detecting the notification of the incoming call, the devicedisplays, in the second region 2302, an accept-call affordance 2310(e.g., a first graphical object). In some implementations, when thedevice detects a selection input directed to the accept-call affordance2310 while there is an incoming call, the device answers the incomingcall. In some implementations, a selection input directed to anaffordance, selectable user interface object, graphical object, or thelike, corresponds to a user touching, tapping, pressing, clicking orotherwise selecting the affordance, selectable user interface object,graphical object, or the like.

In some implementations, in response to detecting the notification ofthe incoming call, the device also displays, in the second region 2302,a reject-call affordance 2312 (e.g., a second graphical object). In someimplementations, when the device detects a selection input directed tothe reject-call affordance 2312 while there is an incoming call, thedevice rejects the incoming call (which may include sending the incomingcall to voicemail).

In some implementations, in response to detecting the notification ofthe incoming call, the device displays incoming call information 2308(e.g., a third graphical object). In some implementations, the incomingcall information 2308 includes a name of the caller, a phone numberassociated with the caller, a business associated with the caller,and/or other information about or associated with the caller.

In some implementations, in response to detecting a selection of theaccept-call affordance 2310, the device accepts (e.g., answers) theincoming call and displays, in the second region 2302, an audioselection affordance and an end-call affordance. In someimplementations, when the device detects a selection input directed tothe end-call affordance while there is an ongoing call, the device endsthe ongoing call. Examples of an audio selection affordance and anend-call affordance are described with respect to FIG. 27.

In example 2305, the event is a notification of a calendar event. Insome implementations, in response to detecting the notification of thecalendar event, the device displays, in the second region 2302, acalendar object 2314 (e.g., a first graphical object) indicatinginformation such as the calendar event date, time, etc. In someimplementations, in response to detecting the notification of thecalendar event, the device displays calendar event information 2316(e.g., a third graphical object). In some implementations, the calendarevent information 2316 includes a name of the calendar event, a starttime of the calendar event, a location of the calendar event, and/orother information about or associated with the calendar event.

In some implementations, one or both of the calendar object 2314 and thecalendar event information 2316 are affordances (e.g., selectable userinterface objects) that, when selected by a user (e.g., by touching,tapping, pressing, clicking, and/or otherwise selecting the graphicalobjects) cause the device to perform an additional action related to theevent. For example, in some implementations, selecting the m calendarobject 2314 and the calendar event information 2316 causes informationabout the calendar event to be displayed in the second region 2302 ofthe display.

In example 2307, the event is a notification of an expiration of atimer. In some implementations, in response to detecting thenotification of the expiration of the timer, the device displays, in thesecond region 2302, affordances such as a timer repeat affordance 2320(e.g., a first graphical object) and/or a timer-stop affordance 2322(e.g., a second graphical object). In some implementations, when thedevice detects a selection input directed to the timer repeat affordance2320, the device initiates a timer having the same duration as theexpired timer. In some implementations, when the device detects aselection input directed to the timer-stop affordance 2322, the devicestops at least one of an audible or a tactile output triggered by theexpiration of the timer.

In some implementations, in response to detecting the notification ofthe expiration of the timer, the device also displays, in the secondregion 2302, timer information 2318 (e.g., a third graphical object). Insome implementations, the timer information 2318 includes textindicating that an audible or a tactile output was triggered by theexpiration of a timer.

In example 2309, the event is a notification of an expiration of analarm (or timer). In some implementations, in response to detecting thenotification of the expiration of the alarm (or timer), the devicedisplays, in the second region 2302, a graphical object 2324 thatoccupies all (or substantially all) of the second region 2302. In someimplementations, the graphical object 2324 is an affordance, and whenthe device detects a selection input directed to the graphical object2324, the device stops at least one of an audible or a tactile outputtriggered by the expiration of the alarm (or timer).

In some implementations, in response to detecting the notification ofthe expiration of the timer, the device also displays, in the secondregion 2302, text information 2326 indicating a function of thegraphical object 2324 (e.g., the text “stop” to indicate that aselection input directed to the graphical object 2324 will stop anactive audible and/or tactile output).

In example, 2311, the event is a notification of a navigationinstruction. In some implementations, in response to detecting thenotification of the navigation instruction, the device displays, in thesecond region 2302, a direction graphic 2332 (e.g., a first graphicalobject) that indicates an upcoming maneuver (e.g., a turn, merge, stop,detour, etc.), navigation information 2328 (e.g., a second graphicalobject) that provides information about the upcoming maneuver (e.g., adistance to the maneuver, a textual description of the maneuver), and anavigation affordance 2330 (e.g., a third graphical object). In someimplementations, when the device detects a selection input directed tothe navigation affordance 2330, the device displays additionalinformation about the navigation (e.g., an estimated time of arrival toa destination, a list of alternative destinations, an opportunity to addor change waypoints, etc.).

In example, 2313, the event is a coupling of a charger to the device. Insuch cases, the device displays a graphical object 2334 indicatingattachment of the charger (e.g., a representation of the charging dock,a lightning bolt, a battery, an electrical plug, or the like).

In some implementations, the occurrence of the event detected by thedevice is a user request to initiate a wireless payment. A user mayinitiate a wireless payment request in various ways. For example, insome implementations, the user may push a button on the device toinitiate the wireless payment request. In some implementations, the usermay place the device proximate to (e.g., within a threshold distance of)a near-field wireless payment system, which the device may detect usinga corresponding near-field wireless communication system. In someimplementations, the user may initiate a request via a second device(e.g., watch, notebook or tablet computer, or the like) that is incommunication with the device.

In some implementations, in response to detecting the request toinitiate the wireless payment, the device initiates a wireless paymentroutine that includes displaying graphical objects on the second regionof the display to guide the user through a payment process, which mayinclude biometric authentication steps, payment card selection steps,and the like. FIG. 24 illustrates example graphical outputs that may beprovided pursuant to such a payment routine.

As shown in the example of FIG. 24, when the device detects the userrequest to initiate the wireless payment at stage 2400, the device isdisplaying, in a second region 2401 of the display (e.g., correspondingto the second region 2100 or 2105), a second graphical user interface2410 (shown as including a graphical representation of the time, thoughit may include different or additional content). In someimplementations, the second region 2401 is blank at stage 2400.

In some implementations, in response to detecting the request toinitiate the wireless payment, at stage 2402, the device displays afirst graphical object 2412 that includes a representation of abiometric authentication process. In some implementations, therepresentation of the biometric authentication process includes agraphic that indicates what type of biometric authentication can approveor authorize the wireless payment. For example, if a facialauthentication system can approve or authorize the wireless payment, thegraphic represents a face. As another example, if a fingerprintauthentication system can approve or authorize the wireless payment, thegraphic represents a fingerprint. Other graphics and biometricauthentication processes are also contemplated, and may be displayed atstage 2402 or at other stages or states of the wireless payment process.For example, in some implementations, the representation of thebiometric authentication process includes an indication that biometricauthentication is required, an indication that biometric authenticationhas failed, and/or an indication that biometric authentication hassucceeded. In some implementations, the biometric authentication isperformed with a biometric sensor integrated into the device such as aface identification sensor, a fingerprint identification sensor, an irisidentification sensor, or the like. In implementations where a biometricauthentication is to be performed by a biometric sensor integrated intothe device, and the device is in a case that covers at least part of thedevice (e.g., the case 1900), the case includes openings, windows,flaps, or other suitable access points for the user to provide theappropriate input to the biometric sensor. For example, inimplementations where a device (e.g., the device 800) includes a facialidentification sensor, a case (e.g., the case 1900) includes an openingthrough which the facial identification sensor can capture an image ofthe user's face (or otherwise optically analyze and/or recognize theuser's face). Openings for fingerprint sensors, iris identificationsensors, or the like, are also provided in protective cases to provideaccess to the biometric sensors, for devices that include such sensors.

In some implementations, in response to detecting the request toinitiate the wireless payment, at stage 2402, the device also displays asecond graphical object 2414 that includes a representation of a paymentcard associated with the wireless payment. In some implementations, therepresentation of the payment card includes information that uniquelyidentifies the particular payment card and/or allows a user todistinguish the payment card from among multiple candidate payment cards(e.g., a color, image, name, number, etc.). In some implementations, asdescribed with respect to FIG. 26, the representation of the paymentcard 2414 is an affordance (e.g., a selectable user interface object)that, when selected by a user, causes a payment card selection interfaceto be initiated.

In some implementations, in response to a successful biometricauthentication, at stage 2404, the device displays a third graphicalobject 2416 that includes a representation of a wireless paymentoperation (e.g., a graphic that prompts the user to place the device onor near a wireless payment device such as a point-of-sale system).

After the user performs the wireless payment operation (e.g., placingthe device on or near a wireless payment device), the device may receivean indication that the wireless payment operation has been completed. Insome implementations, in response to receiving the indication that thewireless payment operation has been completed, the device displays, atstage 2406, a fourth graphical object 2418 that indicates a confirmationthat the payment operation has been completed (e.g. a checkmark, smileyface, or the like). In some implementations, the device continues todisplay the representation of the payment card 2414 at stage 2406.

In some implementations, after a device detects a request to initiate awireless payment, the device requires a user selection of a displayedaffordance in order to proceed with the wireless payment routine. Forexample, if the request to initiate a wireless payment corresponds to adetermination that the user has placed the device proximate to (e.g.,within a threshold distance of) a near-field wireless payment system(e.g., the user attempted to make a wireless payment with the device),the device may require the user to take another explicit physical actionin order to proceed with the wireless payment routine. This may mitigateaccidental or unintentional initiations of wireless payments.

FIG. 25 illustrates example graphical outputs that may be providedpursuant to such a payment routine. As shown in the example of FIG. 25,when the device detects the user request to initiate the wirelesspayment at stage 2500, the device is displaying, in a second region 2501of the display (e.g., corresponding to the second region 2100 or 2105),a second graphical user interface 2510 (shown as including a graphicalrepresentation of the time, though it may include different oradditional content). In some implementations, the second region 2501 isblank at stage 2500.

In some implementations, in response to detecting the request toinitiate the wireless payment (e.g., detecting that the user has placedthe device near a near-field wireless payment system in an attempt tomake a wireless payment), at stage 2502, the device displays anaffordance 2512 (e.g., selectable user interface object). When thedevice detects a user selection of the affordance 2512 (e.g., a tap,press, touch, or other suitable selection input), wireless payment isauthorized and the wireless payment routine proceeds.

Once the affordance 2512 has been selected by the user, at stage 2504,the device displays a first graphical object 2516 that includes arepresentation of a biometric authentication process, and a secondgraphical object 2514 that includes a representation of a payment cardassociated with the wireless payment. The first and second graphicalobjects 2516, 2514 may correspond to the first and second graphicalobjects 2416 and 2414.

In some implementations, in response to a successful biometricauthentication and after the device receives an indication that thewireless payment operation has been completed, the device displays, atstage 2506, a third graphical object 2518 that indicates a confirmationthat the payment operation has been completed (e.g. a checkmark, smileyface, or the like). In some implementations, the device continues todisplay the representation of the payment card 2514 at stage 2506. Inthe routine depicted in FIG. 25, the graphical object representing awireless payment operation (e.g., a graphic that prompts the user toplace the device on or near a wireless payment device such as apoint-of-sale system) may be omitted, as the request to initiate awireless payment may have been initiated by the user taking that sameaction.

In some cases, a user can interact with the content displayed in thesecond region of a display during a wireless payment routine in order toselect and/or control parameters of the payment process, such as toselect a payment card or payment source from a plurality of candidates.FIG. 26 illustrates an example interaction with a graphical elementduring a payment routine to select a payment card or method.

As shown in the example of FIG. 26, when the device detects the userrequest to initiate the wireless payment at stage 2604, the device isdisplaying, in a second region 2601 of the display (e.g., correspondingto the second region 2100 or 2105), a second graphical user interface2616 (shown as including a graphical representation of the time, thoughit may include different or additional content). In someimplementations, the second region 2601 is blank at stage 2604.

In some implementations, in response to detecting the request toinitiate the wireless payment, at stage 2606, the device displays afirst graphical object 2618 that includes a representation of abiometric authentication process. In response to detecting the requestto initiate the wireless payment, at stage 2606, the device alsodisplays a second graphical object 2620 that includes a representationof a payment card associated with the wireless payment. In someimplementations, the representation of the payment card includesinformation that uniquely identifies the particular payment card and/orallows a user to distinguish the payment card from among multiplecandidate payment cards (e.g., a color, image, name, number, etc.).

In some implementations, the representation of the payment card 2620 isan affordance (e.g., a selectable user interface object) that, whenselected by a user, as indicated by touch event 2622 on therepresentation of the payment card 2620, causes a payment card selectioninterface to be initiated. In some implementations, the representationof the payment card 2620 corresponds to an available payment card ormethod, and continuing the payment process without providing the touchevent 2622 on the representation of the payment card 2620 (e.g., byproceeding with biometric authentication) results in the payment processproceeding using the payment card represented by the representation ofthe payment card 2620. In some implementations, the payment processcannot proceed until the user provides the touch event 2622 and selectsa particular payment card from the candidate payment cards or methods.

Stage 2608 shows an example payment card selection interface thatappears in response to detecting a selection of the representation ofthe payment card 2620. The payment card selection interface displays aplurality of graphical objects representing a plurality of payment cards2626 (or other payment methods, sources, or the like). A user can scrollthrough the plurality of representations of payment cards 2626 byapplying a gesture input. For example, a swipe gesture (represented by atouch event 2622 and movement 2624) causes the representations ofpayment cards 2626 to scroll in the direction of the gesture (e.g., tothe left, as shown in FIG. 26), allowing the user to see additionalpayment card options.

The user selects a payment card from the plurality of representations ofpayment cards 2626, as illustrated by the selection input 2628 directedto the payment card 2626-4 at stage 2610. Upon detecting the selectionof the payment card 2626-4, the device proceeds to a next operation inthe payment routine. For example, if a biometric authentication is stillrequired, the device displays a representation of a biometricauthentication process to prompt the user to perform a biometricauthentication. If a biometric authentication process has beensuccessfully completed, at stage 2612, the device displays the selectedpayment card 2626-4 and a graphical object 2630 that includes arepresentation of a wireless payment operation (e.g., a graphic thatprompts the user to place the device on or near a wireless paymentdevice such as a point-of-sale system).

After the user performs the wireless payment operation (e.g., placingthe device on or near a wireless payment device), the device may receivean indication that the wireless payment operation has been completed. Insome implementations, in response to receiving the indication that thewireless payment operation has been completed, the device displays, atstage 2614, a graphical object 2632 that indicates a confirmation thatthe payment operation has been completed (e.g. a checkmark, smiley face,or the like). In some implementations, the device continues to displaythe representation of the payment card 2626-4 at stage 2614.

FIG. 26 illustrates an example in which a user may interact withgraphical objects displayed in a second region of a display of a devicewhile the device is in a protective case with a window that allowsaccess to the second region of the display through an opening. FIG. 27depicts another example of a user interaction with the second region ofthe display. In particular, FIG. 27 relates to an incoming callnotification that may appear in the second region, and user interactionsthat result in accepting the incoming call.

As shown in the example of FIG. 27, when the device detects an incomingcall, at stage 2704, the device is displaying, in a second region 2701of the display (e.g., corresponding to the second region 2100 or 2105),a second graphical user interface 2702 (shown as including a graphicalrepresentation of the time, though it may include different oradditional content). In some implementations, the second region 2701 isblank at stage 2704.

In some implementations, in response to detecting an incoming call, thedevice displays an affordance 2714 in the second region 2701 of thedisplay, along with graphical objects 2715 (e.g., an arrow in a channel)that indicate or suggest a gesture input that will result in acceptanceof the call. For example, as shown in stages 2708 and 2710, a swipegesture (represented by a touch event 2716 and movement 2718) causes theaffordance 2714 to slide along a direction). In response to the devicedetecting that the gesture has been completed (e.g., the affordance 2714has been moved to a target location (e.g., the end of the channel, asshown in stage 2710), the device accepts the incoming call.

Upon accepting the incoming call, the device displays, in the secondregion 2701, an end-call affordance 2720, as shown in stage 2712. Thedevice also optionally displays an audio selection affordance 2722. Theaudio selection affordance 2722, when selected, causes the device todisplay affordances of available audio output options (e.g., forconventional placement of the device to a user's ear, speakerphone,headphones, or the like). The user can select a desired audio option,which will cause the device to initiate that audio option and return tothe graphical user interface shown at stage 2712. Selection of theend-call affordance 2720 results in the call being terminated. Thedevice also optionally displays information 2724 about the call, such asan elapsed call time, a name of the caller, a phone number of thecaller, or the like. In some implementations, information 2724 mayinclude scrolling text to display information about the call.

Another example event that may be detected when a device is in aprotective case, and that may therefore cause a graphical object to bedisplayed in a second region of the display, is an initiation of avoice-based digital assistant. A voice-based digital assistant may beinitiated in several ways. In some implementations, it is initiatedthrough a voice-command (e.g., a user speaking a word or phrase that thedevice detects). In some implementations, it is initiated throughoperation of a physical input on the device (e.g., a user pressing abutton of the device) or selection of an affordance on a display of thedevice. In response to initiation of the voice-based digital assistant,the device receives, via a microphone, a voice input from the user,determines the content of the voice input, and performs an action (orforegoes performing an action) in response to the content of the voiceinput.

FIG. 28 illustrates a series of graphical outputs that may be producedin response to initiation and use of a voice-based digital assistant.When the device detects an initiation of a voice-based digitalassistant, at stage 2804, the device is displaying, in a second region2801 of the display (e.g., corresponding to the second region 2100 or2105), a second graphical user interface 2802 (shown as including agraphical representation of the time, though it may include different oradditional content). In some implementations, the second region 2801 isblank at stage 2804.

In some implementations, in response to detecting the initiation of thevoice-based digital assistant, the device displays a graphical object2812 in the second region 2801 of the display. In some implementations,the graphical object 2812 is animated in accordance with a voice inputreceived by the device. For example, FIG. 28 shows the graphical object2812 as a wave or spectrogram type graphic, which undulates, fluctuates,or otherwise moves in accordance with the voice input. In someimplementations, the animation of the graphical object 2812 reflectsactual audio content of the voice input (e.g., peaks in volume arereflected as peaks in the graphical object 2812). In someimplementations, the graphical object 2812 is animated when the voiceinput is received (and is responsive to the voice input), but theanimation is not based on audio content (e.g., the volume or content ofthe voice input does not define the exact shape or peaks of thegraphical object 2812).

After or during the voice input, the device displays, at stage 2808, atextual representation 2814 of the voice input. In some implementations,the entire textual representation 2814 is displayed in its entirety whena speech-to-text process has been completed on an entire voice input. Insome implementations, the textual representation 2814 is displayed inreal-time, displaying partial results of a speech-to-text process asthose partial results are available (and optionally while the voiceinput is ongoing).

Upon completion of the speech-to-text operation, and after displayingthe textural representation 2814, the device displays a graphical object2816 that includes an output of the voice-based digital assistant. Theoutput is based on the content of the speech-to-text operation. Forexample, as shown in FIG. 28, the input to the voice-based digitalassistant was “what's the weather,” and the output from the voice-baseddigital assistant is weather data. Other types of inputs and outputs arealso contemplated.

In some implementations, a user can interact with a second graphicalinterface that is displayed in a second region of a display in order tocause the device to display different or additional graphical userinterfaces or other content. FIGS. 29A-29B illustrate examples of suchinteractions with the second region of a display.

FIG. 29A shows, at stage 2904, the second region 2901 (e.g.,corresponding to the second region 2100 or 2105) displaying a secondgraphical user interface 2902 (shown as including a graphicalrepresentation of the time, though it may include different oradditional content). As noted above, the second graphical user interface2902 displays third graphical content (e.g., a clock display), which isdifferent from the second graphical content that was displayed in thesecond region of the display as part of the first graphical userinterface.

In some implementations, the device detects a gesture on the secondgraphical user interface 2902, as represented by the touch input 2910and arrow 2912 at stages 2904 and 2906. As depicted, the gesture is aslide or swipe gesture in the direction indicated by the arrow 2912. Thetouch input 2910 may be provided at any location in the second graphicaluser interface.

In response to detecting the gesture (e.g., the swipe gesture as shownin stages 2904 and 2906), the device displays fourth graphical content2914, different from the third graphical content, in the second region2901 of the display. In some implementations, the fourth graphicalcontent appears to slide into the second region of the display 2901 froma right side of the second region 2901, while the third graphicalcontent (e.g., the clock) appears to slide out of the second region 2901from a left side of the second region 2901. In this way, both the thirdand fourth graphical content move in accordance with the motion of thegesture. Upon completion of the gesture, the fourth graphical content2914 of the third graphical user interface is displayed in the secondregion 2901 of the display, as shown at stage 2908.

In some implementations, the fourth graphical content 2914 includes aplurality of affordances (e.g., selectable user interface objects). Forexample, as shown at stage 2908, the fourth graphical content 2914includes a first affordance 2916 (shown as a do-not-disturb modeselection affordance), a second affordance 2918 (shown as a wirelesspayment initiation affordance), a third affordance 2920 (shown as avolume control selection affordance), and a fourth affordance (shown asa ring/silent selection affordance). Selection of an affordance, whichare selectable user interface objects, causes the device to take anaction (or forgo taking an action) associated with the affordance. Forexample, selection of the second affordance 2918 causes the device toinitiate a wireless payment operation.

FIG. 29B illustrates another example interactions with the second regionof a display while the second graphical user interface is displayed.While FIG. 29A illustrates a swipe gesture in the left-hand direction,FIG. 29B illustrates a swipe gesture in the right-hand direction.Swiping in the opposite direction can cause yet another differentgraphical user interface to be displayed.

In particular, FIG. 29B shows, at stage 2930, the second region 2901(e.g., corresponding to the second region 2100 or 2105) displaying asecond graphical user interface 2902 (shown as including a graphicalrepresentation of the time, though it may include different oradditional content).

In some implementations, the device detects a gesture on the secondgraphical user interface 2902, as represented by the touch input 2936and arrow 2938 at stages 2930 and 2932. As depicted, the gesture is aslide or swipe gesture in the direction indicated by the arrow 2938(e.g., to the right, in the opposite direction as the gesture in FIG.29A). The touch input 2936 may be provided at any location in the secondgraphical user interface.

In response to detecting the gesture (e.g., the swipe gesture as shownin stages 2930 and 2932), the device displays fifth graphical content2940, different from the fourth graphical content 2914 (and differentfrom the third graphical content of the second graphical user interface2902), in the second region 2901 of the display. In someimplementations, the fifth graphical content 2940 appears to slide intothe second region of the display 2901 from a left side of the secondregion 2901, while the third graphical content (e.g., the clock) appearsto slide out of the second region 2901 from a right side of the secondregion 2901. In this way, both the third and fifth graphical contentmove in accordance with the motion of the gesture. Upon completion ofthe gesture, the fifth graphical content 2940 of the fourth graphicaluser interface is displayed in the second region 2901 of the display, asshown at stage 2934.

In some implementations, the fifth graphical content 2940 includes mediainformation and a set of media playback controls. As shown in FIG. 29B,for example, the fifth graphical content 2940 includes an album artgraphic, media playback controls (including, for example, skip forward,skip backwards, and play), and a volume control selection affordance.

As described above, the second graphical user interface may include abackground graphic that has a color that matches the case to which thedevice is coupled. In some implementations, the third and fourthgraphical user interfaces have the same background graphic (e.g., thebackgrounds have the same color as the case to which the device iscoupled).

In some implementations, the particular graphical objects that aredisplayed in the second region of a display (e.g., when a protectivecase with a window is attached) can be changed by a user. FIG. 30illustrates an example for changing between different graphical objectsin a second region 3001 of a display (e.g., corresponding to the secondregion 2100 or 2105). As shown, the second region 3001 displaysgraphical objects (which may be affordances) including a date object3008 (e.g., indicating the current day, date, month, etc.), a clockobject 3010 (e.g., indicating the current time), and a weather object3012 (e.g., indicating current and/or predicted weather conditions).

In some implementations, a user can change the graphical objects thatare displayed in the second region 3001 by swiping through variouscandidate graphical objects. The candidate graphical objects include,for example, an alarm clock object 3014, an analog clock object 3018, atemperature display object 3024, a stock object 3022, a large-formatclock object 3020, and a message application object 3016. The candidategraphical objects shown in FIG. 30 are merely examples, and more ordifferent objects may be included. Further, in some implementations,some or all of the graphical objects shown in FIG. 30 are affordances,or selectable user interface objects. For example, in response todetecting a selection (e.g., touch, tap, press, etc.) of the messageapplication object 3016, the device may display a text messaginginterface.

In some implementations, the graphical objects that are displayed in thesecond region 3001 are changed in response to gestures. For example, insome implementations the device detects a gesture initiated on a firstgraphical object (e.g., a downward swipe on the date object 3008), and,in response to detecting the gesture, replaces the first graphicalobject with a second graphical object different than the first graphicalobject (e.g., the alarm clock object 3014).

In some implementations, the candidate graphical objects are logicallyarranged in columns, such as columns 3002, 3004, and 3006. Thearrangement of the candidate graphical objects may define what gesturescause what graphical objects to be displayed. For example, a downwardswipe initiated on the date object 3008 would result in the date object3008 being replaced with the alarm clock object 3014, while an upwardswipe initiated on the date 3008 would cause the message applicationobject 3016 to be displayed instead.

In some implementations, a user can select what graphical objects are inthe columns, and the location of the graphical objects in the columns.As one example, a user could have one column include graphical objectshaving multiple different clock display types (e.g., analog, digital,different colors, different sizes, different time zones, etc.), so thatthe user can easily select a particular graphical object by swipingthrough the column when the device is in the case.

While FIG. 30 illustrates one example set of graphical objects, the samefunctionality described with respect claim 30 may apply equally to othergraphical objects displayed in the second region of a display. Forexample, with reference to FIG. 29A, a user can optionally change thedisplayed affordances by initiating a gesture on a displayed affordance(e.g., the first affordance 2916). In response to detecting the gesture,the first affordance will be replaced with a different affordance.

In some implementations, information displayed in a second region of adisplay and viewable through an opening in a protective case may prompta user to remove the device from the case to interact with or view alarger area of the display. For example upon seeing a notification onthe display through the opening in the case, a user may partially removethe device from the case to reveal a portion of the display. The devicecan detect that it is partially removed, and display, on the portion ofthe display that is visible due to the partial removal from the case,information related to the notification seen through the opening in thecase.

FIG. 31 illustrates an example of a device displaying additionalinformation in response to being at least partially removed from a case.In particular, at stage 3100, the device 802 is coupled to the case1910, and the second graphical user interface 1915 is displayed on thesecond region of the display. At stage 3102, the device 802 has detectedan occurrence of an event, such as a notification of a received message(e.g., an email, a text message, etc.), and, in response, has displayedgraphical content 3106 in the second region of the display. As shown,the displayed graphical content 3106 is a notification of the event(e.g., an indication that the message was received and information aboutthe message).

After displaying the graphical content 3106, the device 802 detects thatit is at least partially removed from the case 1910 such that a thirdregion 3108 of the display is not covered by the case 1910, as shown instage 3103. In some implementations, the third region 3108 correspondsto an area of the display that is first revealed as the device 802 isremoved from the case 1910. In some implementations, the third region3108 is a specified size (e.g., half of the display area, one third ofthe display area). In other implementations, the size of the thirdregion 3108 corresponds to the amount of the display that is not coveredby the case 1910.

In response to detecting that the device 810 is at least partiallyremoved from the case 1910, the device 810 displays graphical content3110 in the third region 3108 of the display, where the graphicalcontent 3110 includes information associated with the event. Thus, forexample, if the event that caused the graphical content 3106 to bedisplayed in the second region of the display is an incoming message,the graphical content 3110 includes information about the incomingmessage (e.g., message content). In some implementations, the user caninteract with the third region 3108 of the display, such as to read themessage, respond to the message, or the like. In some implementations,in response to detecting that the device 802 has been reinserted intothe case 1910, the device 802 displays the second graphical userinterface 1915 in the second region of the display.

The location on a display where graphical content is displayed maydepend on whether or not the device is coupled to a case or not coupledto a case. For example, with reference to FIGS. 32A and 32B, a devicedetects an occurrence of an event. As shown, the event is an incomingcall, though in other cases the event is an incoming message, a requestto initiate a wireless payment, an expiration of a timer, a coupling ofa charger to the device, or the like.

With reference to FIG. 32A, which shows the device 802 not coupled tothe case 1910, in response to detecting the occurrence of the event(here, an incoming call), in accordance with a determination that a case(e.g., the case 1910) is not coupled to the device 802, the device 802displays, in a first region 3201 of the display, first graphical content3202 associated with the event. The first region 3201 of the displayincludes a region of the display that is covered by the case 1910 whenthe case 1910 is coupled to the device 802. In some implementations, thefirst region 3201 also includes a portion of the display that is notcovered by the case 1910. In some implementations, the first graphicalcontent 3202 includes an affordance (e.g., a selectable user interfaceobject), such as an accept-call affordance, a reject-call affordance, ora timer-stop affordance. The affordance may have a first appearance.

With reference to FIG. 32B, which illustrates the device 802 coupled tothe case 1910, in accordance with a determination that the case 1910 iscoupled to the device 802, the device 802 displays, in a second region3207 of the display, which is different than the first region of thedisplay, second graphical content 3204 associated with the event. Thesecond region 3207 of the display, which corresponds to the secondregion 2105, is visible through an opening 1912 in the case when thecase is coupled to the device 802. Thus, the same type of event willproduce a graphical output at a different location on the displaydepending on whether or not a case is attached to the device. In someimplementations, the second graphical content 3204 is different than thefirst graphical content 3202.

In some implementations, the second graphical content 3204 also includesan affordance, such as an accept call affordance (in the case of anincoming call notification). In some implementations, the affordance inthe second graphical content 3204 has an appearance that is the same asthe affordance of the first graphical content 3202. In someimplementations, the affordance in the second graphical content 3204 hasan appearance that is different from the affordance of the firstgraphical content 3202. For example, in some implementations, theaffordance in the first graphical content 3202 resembles a button (FIG.32A), and the affordance in the second graphical content is a slider(FIG. 32B).

In some implementations, in the case of an incoming call notification,the second graphical content includes text including information aboutthe incoming call. In some implementations, the information about theincoming call includes a caller name and/or a caller number. In someimplementations, the text scrolls across a portion of the display.

In the case of an incoming call notification, and in response todetecting a selection of the accept-call affordance in the secondgraphical content 3204, the device accepts the incoming call anddisplays displaying an audio selection affordance and an end-callaffordance (e.g., as shown at stage 2712 of FIG. 27).

As noted above, one of the events that may be detected by the device 802(and cause the device 802 to produce different graphical content basedon whether or not the case is coupled to the device) is a user requestto initiate a wireless payment. As described above with respect to FIGS.24-26, for example, the user request may be initiated by a user pushinga button on the device, placing the device proximate to (e.g., within athreshold distance of) a near-field wireless payment system, initiatinga request via a second device (e.g., watch, notebook or tablet computer,or the like), or the like. In accordance with a determination that thecase 1910 is not attached (as shown in FIG. 32A), graphical objectsrelating to a wireless payment process are displayed in the first region3201 of the display. In accordance with a determination that the case1910 is attached (as shown in FIG. 32B), graphical objects relating tothe wireless payment process are displayed in the second region 3207 ofthe display. For example, in some implementations, in response todetecting a user request to initiate a wireless payment, the secondgraphical content 3204 includes a representation of a payment cardassociated with the wireless payment (as described above with respect toFIGS. 24-27).

In some implementations, the second graphical content 3204 includes arepresentation of a biometric authentication process (as described abovewith respect to FIGS. 24-27). In some implementations, therepresentation of the biometric authentication process includes anindication that biometric authentication is required, an indication thatbiometric authentication has failed, and/or an indication that biometricauthentication has succeeded. In some implementations, the biometricauthentication is performed with a biometric sensor integrated into thedevice such as a face identification sensor, a fingerprintidentification sensor, an iris identification sensor, or the like.

In some implementations, the second graphical content 3204 includes anaffordance, and user selection of the affordance authorizes the wirelesspayment. For example, the second graphical content 3204 may include theaffordance 2512 shown in FIG. 25, the selection of which authorizes thewireless payment.

In some implementations, prior to detecting the occurrence of the event(e.g., the incoming call, the request to initiate a wireless payment),and in accordance with a determination that the case is coupled to thedevice, the device displays third graphical content 3205 in the secondregion of the display. As shown, the third graphical content 3205 is agraphical representation of the time (e.g., a clock). In response todetecting the occurrence of the event, the size of the third graphicalcontent is reduced, and a portion of the second graphical content (e.g.,graphical content associated with the event, such as an accept-callaffordance) is positioned in a portion of the second region of thedisplay occupied by the third graphical content 3205 prior to thereduction in size of the third graphical content 3205. Thus, forexample, the graphical representation of the current time is reduced insize (and moved to a different location in the second region of thedisplay), while an accept-call affordance is displayed where thegraphical representation of the current time used was previouslydisplayed.

Another example event that may be detected by the device 802 (and causethe device 802 to produce different graphical content based on whetheror not the case is coupled to the device) is an expiration of a timer.In accordance with a determination that the case 1910 is not attached(as shown in FIG. 32A), timer information, including timer progress,timer-stop affordances, and the like, are displayed in a first region3201 of the display.

In some implementations, prior to detecting the occurrence of the event(e.g., the expiration of the timer), and in accordance with adetermination that the case 1910 is coupled to the device, the device802 displays a progress of the timer in the second region 3207 of thedisplay. In some implementations, displaying the progress of the timerincludes displaying a timer countdown. In response to detecting theexpiration of the timer, and in accordance with a determination that thecase 1910 is coupled to the device 802, the device displays, in thesecond region 3207 of the display, an affordance. In someimplementations, user selection of the affordance stops at least one ofan audible or a tactile output triggered by the expiration of the timer.

Another example event that may be detected by the device 802 (and causethe device 802 to produce different graphical content based on whetheror not the case is coupled to the device) is a coupling of a charger tothe device. For example, in accordance with a determination that thecase 1910 is not attached (as shown in FIG. 32A), first graphicalcontent (e.g., the visual indication 906) indicating the attachment ofthe charger is displayed in a first region 3201 of the display. Inresponse to detecting the attachment of the charger, and in accordancewith a determination that the case 1910 is coupled to the device 802,the device displays, in the second region 3207 of the display, secondgraphical content comprising a graphical representation of a chargingfunction (e.g., a lightning bolt, a plug, a battery, etc.).

In some implementations, whether or not a case is attached to a devicemay correspond to a mode of operation of the device. For example, insome implementations, the device is considered in a first mode ofoperation when the device is not coupled to a case, and in a second modeof operation when the device is coupled to the case.

In some implementations, while the device (e.g., the device 802) isoperating in a first mode of operation, the device 802 detects a firstoccurrence of an event. In some implementations, the event is anattachment of a charging accessory, an expiration of a timer, anincoming call, or any other event described herein. In response todetecting the first occurrence of the event, the device 802 displays, ina first region 3201 of the display, first graphical content associatedwith the event (e.g., an incoming call notification, an accept-callaffordance, a timer-stop affordance, an indication that a charger hasbeen attached).

In some implementations, the device 802 detects a coupling of a case(e.g., the case 1910) to the device. For example, the device 802detects, with a near-field wireless communication system, a near-fieldwireless communication antenna of the case. In response to detecting thecoupling of the case 1910 to the housing of the device 802, the device802 transitions from the first mode of operation (e.g., a case-off mode)to a second mode of operation (e.g., a case-on mode).

While the device 802 is operating in the second mode of operation andwhile the case 1910 is coupled to the housing of the device, the device802 detects a second occurrence of the event (e.g., a second incomingcall notification, a second accept-call affordance, a second timer-stopaffordance, a second indication that a charger has been attached), andin response to detecting the second occurrence of the event, the device802 displays, in a second region 3207 of the display different than thefirst region of the display, second graphical content associated withthe event (e.g., an incoming call notification, an accept-callaffordance, a timer-stop affordance, an indication that a charger hasbeen attached), where the second graphical content is different from thefirst graphical content. As described above, at least a portion of thefirst region 3201 of the display is covered by the case 1910 when thecase 1910 is coupled to the device 802, and the second region 3207 ofthe display is visible through an opening 1912 in the case 1910 when thecase is coupled to the device 802.

FIG. 33 is a flow chart of an example method 3300 that includesdisplaying a visual indication on a computer system in response to anattachment of an accessory to the computer system. In someimplementations, the method 3300 is performed at a computer system witha display, a housing, and an attachment mechanism. As used herein, acomputer system with a display, housing, and attachment mechanism mayalso be referred to as an electronic device (or simply device). Examplesof such computer systems include, for example, electronic devices 100,800, and 802.

In some implementations, the computer system detects (3302) attachmentof an accessory to the computer system, where the accessory, whileattached, has a predetermined orientation relative to the attachmentmechanism. FIG. 9B, for example, illustrates a charging accessory 804attached to a device 800 in a predetermined orientation. In someimplementations, the attachment mechanism is a magnetic attachmentmechanism.

In some implementations, in response to detecting the attachment of theaccessory to the computer system, and in accordance with a determinationthat the accessory is a first accessory with first physical dimensions,the computer system displays (3304), on the display, a first visualindication that the accessory has been attached to the computer system,wherein the first visual indication indicates at least one property ofthe first physical dimensions. In some implementations, the firstphysical dimensions are a size, a length, a width, or a shape of theaccessory. For example, FIG. 9C illustrates the device 800 displaying avisual indication 906 (e.g., a first visual indication) indicating thatthe charging accessory 804 has been attached to the computer system. Thevisual indication 906 includes a property of the physical dimensions ofthe charging accessory 804. For example, the charging accessory 804 hasa circular shape (e.g., a first physical dimension), and the visualindication 906 has a circular graphical element (e.g., indicating aproperty (e.g., shape) of the first physical dimension of the chargingaccessory 804).

In some implementations, in response to detecting the attachment of theaccessory to the computer system, and in accordance with a determinationthat the accessory is a second accessory with second physical dimensionsthat are different from the first physical dimensions, the computersystem displays (3306), on the display a second visual indication thatthe accessory has been attached to the computer system. In someimplementations, the second physical dimensions are a size, a length, awidth, or a shape of the accessory.

The second visual indication indicates (3308) at least one property ofthe second physical dimensions, and the second visual indication isdifferent from the first visual indication (3310). For example, FIG. 16Aillustrates the device 800 displaying a visual indication 1600indicating that the auxiliary battery accessory 808 has been attached tothe computer system. The visual indication 1600 includes a property ofthe physical dimensions of the auxiliary battery accessory 808. Forexample, the auxiliary battery accessory 808 has a square shape (e.g., asecond physical dimension), and the visual indication 1600 has a squaregraphical element (e.g., indicating a property (e.g., shape) of thesecond physical dimension of the auxiliary battery accessory 808).

In some implementations, the first accessory has a first shape and thesecond accessory has a second shape, and the first visual indication hasa first graphical element having the first shape and the second visualindication has a second graphical element having the second shape. Insome implementations, the first accessory has a first size and thesecond accessory has a second size, and the first visual indication hasthe first size and the second visual indication has the second size. Forexample, FIGS. 9B-9C show a first accessory (e.g., the charging dock804) having a first shape and a first size, and the first visualindication (e.g., visual indication 906, FIG. 9C) having the same shapeand size as the first accessory, and FIG. 13C shows a second accessory(e.g., the auxiliary battery accessory 808) having a second shape and asecond size, and the second visual indication (e.g., visual indication1300) having the same shape and size as the second accessory. FIG. 16Bshows another accessory (e.g., the wallet accessory 806) and acorresponding visual indication 1604 having the same size and shape asthe wallet accessory 806, which is different than the size and shape ofthe first accessory.

In some implementations, the first accessory is shorter than the secondaccessory in a respective dimension, and the first visual indication isshorter than the second visual indication in the respective dimension.In some implementations, the first visual indication occupies less thanan entire area of the display and the second visual indication occupiesan entire area of the display. For example, FIG. 13C shows a secondaccessory (e.g., the auxiliary battery accessory 808) that is shorterthan a first accessory (e.g., the charging dock 804, FIGS. 9A-9C), and asecond visual indication (e.g., visual indication 1300) that is shorterthan the first visual indication (e.g., the visual indication 906, FIG.9C). In some implementations, the second accessory is a protective case(e.g., the cases 810, 812 in FIG. 8, and/or cases 1900, 1910 in FIGS.19A-19B) for the computer system.

In some implementations, the first visual indication and the secondvisual indication include at least one common element (e.g., thegraphical elements 910, 1010 in FIGS. 9C and 10C). In someimplementations, the at least one common element (e.g., the graphicalelements 910, 1010 in FIGS. 9C and 10C) is displayed at a location thatcorresponds to a location of the attachment mechanism in the computersystem (e.g., the attachment mechanisms 814-1, 814-2, FIGS. 9C and 10C).In some implementations, the at least one common element is displayed ina shape that corresponds to a shape of the attachment mechanism in thecomputer system. For example, the graphical elements 910, 1010 (FIGS. 9Cand 10C) are circular, as are the attachment mechanisms 814-1, 814-2(FIGS. 9C and 10C).

In some implementations, the method 3300 further includes, while theaccessory (e.g., a protective case 810, FIG. 15A) is attached to thecomputer system, detecting attachment of an additional accessory (e.g.,charger 804, FIG. 15A) to the computer system, where the additionalaccessory, while attached, has a predetermined orientation relative tothe attachment mechanism, and, in response to detecting the attachmentof the additional accessory to the computer system and in accordancewith a determination that the additional accessory is a third accessorywith third physical dimensions, displaying, on the display, a thirdvisual indication (e.g., the visual indication 906, FIG. 15B) indicatingthat the additional accessory has been attached to the computer system.In some implementations, the third visual indication indicates at leastone property of the third physical dimensions and is different from thefirst visual indication and the second visual indication. For example,attachment of the case 810 causes display of a visual indicationoccupying the entire display (shown in FIG. 14B), attachment of thecharging dock 804 causes display of a visual indication 906 with acircle shape corresponding to the size and shape of the charging dock804 (shown in FIG. 15B), and attachment of an auxiliary batteryaccessory causes display of a visual indication 1300 with a square shapecorresponding to the size and shape of the auxiliary battery accessory808 (shown in FIG. 13C).

In some implementations, the method 3300 further includes displaying, onthe display, a graphical user interface (e.g., first graphical userinterface 1101, FIGS. 11A-11B), and the first visual indication (e.g.,the visual indications 1100, 1102) overlies at least a portion of thegraphical user interface. In some implementations, the first visualindication is a translucent graphical object (e.g., object 1106, FIG.11A) and at least a portion of the graphical user interface (e.g.,graphical object 1104-2, FIG. 11A) is visible through the translucentgraphical object.

In some implementations, the method further includes in accordance witha determination that the computer system is in a first state when theattachment of the accessory is detected, displaying the first visualindication in accordance with the determination that the accessory isthe first accessory and displaying the second visual indication inaccordance with the determination that the accessory is the secondaccessory. In accordance with a determination that the computer systemis in a second state, different from the first state, when theattachment of the accessory is detected, forgoing display of the firstvisual indication and/or the second visual indication. In someimplementations, the first state corresponds to the computer systembeing locked, the computer system displaying a home screen userinterface, the computer system displaying a wake screen or lock screen,or the computer system displaying a system user interface. In someimplementations, the second state corresponds to the computer systembeing unlocked, or the computer system displaying an application userinterface. FIG. 18A, for example, shows a device 800 displaying a visualindication 1802 when an accessory is attached and the device is in afirst state (e.g., displaying a lock screen), and FIG. 18B shows thedevice 800 foregoing display of the visual indication 1802 when thedevice is in a second state (e.g., displaying a home screen).

In some implementations, the first visual indication and the secondvisual indication include information associated with the accessory(e.g. information 1602, 1603, FIG. 16A, and information 1606, FIG. 16B).In some implementations, the information includes a name of an owner ofthe accessory, state of charge of a battery associated with theaccessory, or a room or location associated with accessory.

In some implementations, the method further includes, in response todetecting the attachment of the accessory to the computer system,producing a non-visual output (e.g., tactile output 1708 and/or audiooutput 1706, FIG. 17B), wherein the non-visual output is produced inaccordance with the determination that the accessory is the firstaccessory and in accordance with the determination that the accessory isthe second accessory. In some implementations, the non-visual output isa tactile output (e.g., a vibration), and/or an audio output (e.g., abeep, tone, song).

In some implementations, the first accessory is a first type ofaccessory (e.g., the charging dock 804, FIG. 8), the second accessory isa second type of accessory different from the first type of accessory(e.g., the wallet accessory 806, FIG. 17B), and the same non-visualoutput (e.g., the tactile output 1708 and/or audio output 1706, FIG.17B) is produced by the computer system when the first accessory isattached to the computer system and when the second accessory isattached to the computer system. In some implementations, the first typeof accessory is a charging dock, a protective case, a wallet accessory,or an auxiliary battery accessory (as described with respect to FIG. 8,for example).

In some implementations, the second visual indication is different fromthe first visual indication in a manner that indicates a differencebetween the first physical dimensions and the second physicaldimensions. For example, the visual indication 1600 indicates the firstphysical dimensions of the auxiliary battery accessory 808 (FIG. 16A),and has different dimensions than the visual indication 1604 in FIG. 16B(which, in turn, indicates the second, different physical dimensions ofthe wallet accessory 806). In some implementations, the first visualindication includes a respective portion (e.g., border 1702, FIG. 17A)that expands (e.g., radiates) outward from a location that correspondsto a location of the attachment mechanism (e.g., attachment mechanism814-1, FIG. 8) in the computer system. FIG. 12 also illustrates anexample visual indication 1201 that includes a boundary 1200 thatexpands (e.g., radiates) outward.

In some implementations, the accessory is at least one of a chargingdock, a wallet accessory, a protective case, and an auxiliary batteryfor charging the computer system (as described with respect to FIG. 8,for example).

In some implementations, the method further includes detectingdetachment of the accessory from the computer system, and in response todetecting the detachment, in accordance with a determination that theaccessory is a first type of accessory, generating a first detach output(e.g., tactile output 1708 and/or audio output 1706, FIG. 17B), and inaccordance with a determination that the accessory is a second type ofaccessory, forgoing generation of the detach output. In someimplementations, generating the detach output includes generating thetactile output and/or audio output indicating detachment of theaccessory (e.g., tactile output 1708 and/or audio output 1706, FIG.17B). In some implementations, forgoing generation of the detach outputincludes foregoing generating a tactile output and/or audio outputindicating detachment of the accessory.

In some implementations, the method further includes detectingdetachment of the accessory from the computer system, and, in responseto detecting the detachment, producing a detach output indicating thatthe accessory has been detached from the computer system. In someimplementations, the detach output includes non-visual output (e.g., atactile output and/or an audio output, FIG. 17B). In someimplementations, the tactile output and/or audio output included in thedetach output is the same as tactile output and/or audio output that isgenerated when the accessory is attached. In some implementations, thetactile output and/or audio output in the detach output is differentfrom tactile output and/or audio output that is generated when theaccessory is attached. In some implementations, the tactile outputand/or audio output in the detach output includes a component of thetactile output and/or audio output that is generated when the accessoryis attached and includes a component that is different from the tactileoutput and/or audio output that is generated when the accessory isattached. For example, in some implementations, the audio output that isgenerated when the accessory is attached is the same as the audio outputthat is generated when the accessory is detached, and the tactile outputthat is generated when the accessory is attached is the same as thetactile output that is generated when the accessory is detached. In someimplementations, the audio output that is generated when the accessoryis attached is different from the audio output that is generated whenthe accessory is detached, and the tactile output that is generated whenthe accessory is attached is the same as the tactile output that isgenerated when the accessory is detached. In some implementations, theaudio output that is generated when the accessory is attached is thesame as the audio output that is generated when the accessory isdetached, and the tactile output that is generated when the accessory isattached is different than the tactile output that is generated when theaccessory is detached. In some implementations, the audio output that isgenerated when the accessory is attached is different than the audiooutput that is generated when the accessory is detached, and the tactileoutput that is generated when the accessory is attached is differentthan the tactile output that is generated when the accessory isdetached.

In some implementations, the detach output includes a visual detachindication (e.g., the visual indication 1710, FIG. 17B). For example, insome implementations the visual detach indication includes a map showinga location where the detachment occurred (e.g., the map 373, FIG. 3P).In some implementations, a visual detach indication is shown when thecomputer system is in a first state (e.g., the computer system isdisplaying a lock screen) and not when the system is in a second state(e.g., the computer is displaying an application graphical userinterface).

In some implementations, the first visual indication is an animatedvisual indication (e.g., the animated visual indication 1700, FIG. 17A,which includes an expanding graphical element 1702), the second visualindication is an animated visual indication, and displaying the visualdetach indication includes, in accordance with a determination that theaccessory is the first accessory, displaying a third visual indicationthat includes a reversal of at least a portion of (or all of) the firstvisual indication (e.g., the animated visual indication 1710, FIG. 17B,which includes a retracting graphical element 1712), and in accordancewith a determination that the accessory is the second accessory,displaying a fourth visual indication that is different from the thirdvisual indication and that includes a reversal of at least a portion of(or all of) the second visual indication. In some implementations, thefirst visual indication includes a first respective portion (e.g.,border 1702, FIG. 17A) that expands (e.g., radiates) outward from alocation that corresponds to a location of the attachment mechanism inthe computer system, the third visual indication includes a secondrespective portion (e.g., border 1712 in FIG. 17B) that retracts inwardto the location that corresponds to the location of the attachmentmechanism in the computer system, and the third visual indication isproduced in accordance with the determination that the accessory is thefirst accessory.

FIG. 34 is a flow chart of an example method 3400 that includesdisplaying graphical user interfaces on a computer system in response toan attachment of a case to the computer system. In some implementations,the method 3400 is performed at a computer system with a display and ahousing. As used herein, a computer system with a display and housingmay also be referred to as an electronic device (or simply device).Examples of such computer systems include, for example, electronicdevices 100, 800, and 802.

In some implementations, the computer system displays (3402) a firstgraphical user interface comprising first graphical content displayed ina first region of the display and second graphical content displayed ina second region of the display, the second region different than thefirst region. For example, FIGS. 19A-19B and FIG. 21 illustrate a device800 displaying a first graphical user interface 1904 that includes firstgraphical content (e.g., application icons) displayed in a first regionof the display (e.g., outside the boundary 2102 in FIG. 21A) and secondgraphical content (e.g., at least part of an application icon) displayedin a second region of the display (e.g., inside the boundary 2102 inFIG. 21A).

The computer system detects (3404) a coupling of a case to the computersystem, where the first region of the display is covered by the case andthe second region of the display is visible through an opening in thecase. FIGS. 19A-19B, for example, illustrate the device 800 beingcoupled to a protective case 1900, where the protective case 1900 has awall that covers the first portion of the display and defines an opening1902 through a wall of the case so that the second region of the displayis visible.

In response to detecting the coupling of the case to the computersystem, the computer system transitions (3406) from displaying the firstgraphical user interface to a second graphical user interface. Thetransition includes ceasing to display (3408) the second graphicalcontent in the second region of the display, and displaying (3410) thesecond graphical user interface on the display, the second graphicaluser interface comprising third graphical content, different from thesecond graphical content, displayed in the second region of the display.For example, FIG. 19A illustrates the device 800 transitioning fromdisplaying application icons (or potions thereof) of a first graphicaluser interface 1904 in the second region of the display (e.g., secondgraphical content), to displaying a second graphical user interface 1905in the second region, where the second graphical user interface 1905includes background graphic 1906 and a foreground graphic 1907 (e.g.,third graphical content). FIG. 19B illustrates the device 802transitioning from displaying application icons (or potions thereof) ofa first graphical user interface 1914 in the second region of thedisplay (e.g., second graphical content), to displaying a secondgraphical user interface 1915 in the second region, where the secondgraphical user interface 1905 includes background graphic 1916 and aforeground graphic 1917 (e.g., third graphical content).

In some implementations, the second graphical content of the secondgraphical user interface includes a background graphic (e.g., backgroundgraphic 1906, FIG. 19A, background graphic 1916, FIG. 19B) and aforeground graphic (e.g., foreground graphic 1907, FIG. 19A, foregroundgraphic 1917, FIG. 19B) on the background graphic. In someimplementations, the background graphic is a color, and the foregroundgraphic is a graphical representation of a current time. In someimplementations, the background graphic has a first color that matches acolor of the case, and the foreground graphic has a second colordifferent than the first color. In some implementations, the backgroundgraphic initially has a first color that matches a color of the case,the foreground graphic initially has a second color different from thefirst color, and displaying the second graphical user interfaceincludes, after displaying the background graphic having the first colorand the foreground graphic having the second color, transitioning thebackground graphic from the first color to a third color.

In some implementations, the method further includes, after displayingthe background graphic having the first color (e.g., background graphic1906 in FIG. 19A, background graphic 1916 in FIG. 19B) and theforeground graphic having the second color (e.g., foreground graphic1907 in FIG. 19A, foreground graphic 1917 in FIG. 19B), transitioningthe foreground graphic from the second color to the first color. In someimplementations, the transition of the foreground graphic from thesecond color to the first color occurs simultaneously with thetransition of the background color. In some implementations, thetransition of the foreground graphic from the second color to the firstcolor occurs after the transition of the background color.

In some implementations, the transition further includes, prior todisplaying the second graphical user interface (e.g., the secondgraphical user interfaces 1905, 1915, FIGS. 19A-19B), displaying a blackbackground graphic in the second region of the display.

In some implementations, the method further includes, while the case iscoupled to the computer system, detecting an occurrence of an event,and, in response to detecting the occurrence of the event, displaying,in the second region of the display, a graphical object associated withthe event. In some implementations, the event is an incoming call, andthe graphical object includes an accept-call affordance (e.g.,affordance 2310 in FIG. 23, affordance 2814 in FIG. 27, graphicalcontent 3204 in FIG. 32B). In some implementations, when the devicedetects a selection input directed to the accept-call affordance whilethere is an incoming call, the device answers the incoming call. In someimplementations, the method further includes detecting a selection ofthe accept-call affordance, and in response to detecting the selectionof the accept-call affordance, accepting the incoming call anddisplaying an audio selection affordance (e.g., audio selectionaffordance 2722 in FIG. 27) and an end-call affordance (e.g., end callaffordance 2720 in FIG. 27). In some implementations, when the devicedetects a selection input directed to the end-call affordance whilethere is an ongoing call, the device ends the ongoing call.

In some implementations, the event is a user request to initiate awireless payment, as described with respect to FIGS. 24-26. In someimplementations, the user request to initiate the wireless payment isinitiated by a user pushing a button on the computer system, placing thecomputer system proximate to (e.g., within a threshold distance of) anear-field wireless payment system, initiating a request via a secondcomputer system (e.g., watch, notebook or tablet computer, or the like),or the like. In some implementations, the graphical object includes arepresentation of a payment card (e.g., the graphical object 2414 inFIG. 24, the graphical object 2514 in FIG. 25, the graphical object 2620in FIG. 26) associated with the wireless payment. In someimplementations, the graphical object includes a representation of abiometric authentication process (e.g., the graphical object 2412 inFIG. 24, the graphical object 2516 in FIG. 25, the graphical object 2618in FIG. 26). In some implementations, the graphical object includes anaffordance (e.g., the affordance 2512, FIG. 25), and user selection ofthe affordance authorizes the wireless payment.

In some implementations, the event is a notification of a receivedmessage (e.g., as shown in example 2301 in FIG. 23, and in FIG. 21). Insome implementations, the event is a coupling of a charger to thecomputer system (e.g., as shown in example 2313 in FIG. 23).

In some implementations, the event is an initiation of a voice-baseddigital assistant, and the graphical object (e.g., the graphical object2812 in FIG. 28) is animated in accordance with a voice input receivedby the computer system.

In some implementations, the event is an expiration of a timer, thegraphical object includes an affordance (e.g., the affordance 2322 inexample 2307 in FIG. 23, the graphical object 2324 in example 2309 ofFIG. 23), and user selection of the affordance stops at least one of anaudible or a tactile output triggered by the expiration of the timer.

In some implementations, the method further includes detecting a gestureon the second graphical user interface (e.g., a slide or swipe gestureindicated by the touch input 2910 and the arrow 2912 in FIG. 29A), and,in response to detecting the gesture, displaying fourth graphicalcontent (e.g., graphical content 2914, FIG. 29A), different from thethird graphical content (e.g., graphical user interface 2902, FIG. 29A),in the second region of the display.

In some implementations, the gesture is a first gesture, and the methodfurther includes detecting a second gesture on the second graphical userinterface (e.g., a slide or swipe gesture indicated by the touch input2936 and the arrow 2938 in FIG. 29B), and, in response to detecting thesecond gesture, displaying fifth graphical content (e.g., graphicalcontent 2940, FIG. 29B), different from the fourth graphical content, inthe second region of the display.

In some implementations, the first gesture is a swipe in a firstdirection (e.g., a first direction indicated by the arrow 2912 in FIG.29A), the fourth graphical content includes a plurality of affordances(e.g., the affordances 2916, 2918, 2920, 2922 in FIG. 29A), the secondgesture is a swipe in a second direction opposite the first direction(e.g., a second direction indicated by the arrow 2938 in FIG. 29B), andthe fifth graphical content includes a set of media playback controls(e.g., the media playback controls of the graphical content 2940 in FIG.29B. In some implementations, the plurality of affordances (which areselectable user interface objects) include a do-not-disturb modeselection affordance (e.g., e.g., affordance 2916 in FIG. 29A), awireless payment initiation affordance (e.g., affordance 2918 in FIG.29A), a volume control selection affordance (e.g., affordance 2920 inFIG. 29A), and/or a ring/silent selection affordance (e.g., affordance2922 in FIG. 29A).

In some implementations, the fourth graphical content includes aplurality of affordances (e.g., graphical objects 3008, 3010, 3012 inFIG. 30, which may be affordances). In some implementations, theplurality of affordances include a first affordance and a secondaffordance, and the method further includes, detecting a gestureinitiated on the first affordance (e.g., a vertical swipe, as describedwith reference to FIG. 30), and, in response to detecting the gesture,replacing the first affordance (e.g., the graphical object 3008 in FIG.30) with a third affordance different than the first affordance (e.g.,the graphical object 3014 in FIG. 30). Gestures such as those describedwith respect to FIG. 30 may also be used to change the affordances inother example user interfaces. For example, affordances in the fourthgraphical content in FIG. 29A can be changed by applying a gesture(e.g., a vertical swipe) to an affordance. In some implementations, theplurality of affordances (which are selectable user interface objects)include a do-not-disturb mode selection affordance (e.g., the affordance2916 in FIG. 29A), a wireless payment initiation affordance (e.g., theaffordance 2918) in FIG. 29A, a volume control selection affordance(e.g., the affordance 2920 in FIG. 29A), and/or a ring/silent selectionaffordance (e.g., the affordance 2922 in FIG. 29A).

FIG. 35 is a flow chart of an example method 3500 that includesdisplaying first or second graphical content on a computer system basedon whether or not a case is coupled to the computer system. In someimplementations, the method 3500 is performed at a computer system witha display and a housing. As used herein, a computer system with adisplay and housing may also be referred to as an electronic device (orsimply device). Examples of such computer systems include, for example,electronic devices 100, 800, and 802.

In some implementations, the computer system detects (3502) anoccurrence of an event. In some implementations, the event is anincoming call, a message notification (e.g., email, text message), anexpiration of a timer, an alarm, or the like.

In response to detecting the occurrence of the event, and in accordancewith a determination that a case is not coupled to the computer system,the computer system displays (3504), in a first region of the display,first graphical content associated with the event. For example, FIG. 32Aillustrates a device 802 detecting an incoming call (e.g., an occurrenceof an event), and displaying an incoming call notification (e.g., firstgraphical content) in a first region of the display.

In response to detecting the occurrence of the event, and in accordancewith a determination that the case is coupled to the computer system,the computer system displays (3506), in a second region of the displaydifferent than the first region of the display, second graphical contentassociated with the event. The first region of the display is covered bythe case when the case is coupled to the computer system (3508), and thesecond region of the display is visible through an opening in the casewhen the case is coupled to the computer system (3510). FIG. 32Billustrates the device 802 detecting the incoming call (e.g., anoccurrence of an event), and displaying an incoming call notification(e.g., second graphical content) in a second region of the display thatis visible through the opening 1912. In some implementations, theincoming call notifications differ both in location and content and/orappearance depending on whether the case is coupled to the computersystem or not coupled to the computer system.

In some implementations, the event is an incoming call, and the secondgraphical content includes an accept-call affordance (e.g., affordance2310 in FIG. 23, affordance 2814 in FIG. 27, graphical content 3204 inFIG. 32B). In some implementations, the method further includesdetecting a selection of the accept-call affordance, and, in response todetecting the selection of the accept-call affordance, accepting theincoming call and displaying an audio selection affordance (e.g., audioselection affordance 2722 in FIG. 27) and an end-call affordance (e.g.,end call affordance 2720 in FIG. 27). In some implementations, thesecond graphical content includes a scrolling text including informationabout the incoming call (e.g., the information 2724 in FIG. 27 mayinclude scrolling text, as described with respect to FIG. 27).

In some implementations, the first graphical content (e.g., the firstgraphical content 3202 in FIG. 32A) is different than the secondgraphical content (e.g., the second graphical content 3204 in FIG. 32B).In some implementations, the first graphical content includes a firstaffordance having a first appearance, the second graphical contentincludes a second affordance having a second appearance, user selectionof the first affordance causes the computer system to perform an action,and user selection of the second affordance causes the computer systemto perform the action. For example, FIGS. 32A and 32B illustrate thefirst graphical content 3202 and the second graphical content 3204having affordances with different appearances but both performing thesame action (e.g., accepting an incoming call).

In some implementations, the event is a user request to initiate awireless payment. FIGS. 24-26 illustrate example graphical content thatmay be displayed in response to a user request to initiate a wirelesspayment.

In some implementations, the second graphical content includes arepresentation of a payment card associated with the wireless payment(e.g., the graphical object 2414 in FIG. 24, the graphical object 2514in FIG. 25, the graphical object 2620 in FIG. 26). In someimplementations, the user request to initiate the wireless payment isinitiated by a user pushing a button on the computer system, placing thecomputer system proximate to (e.g., within a threshold distance of) anear-field wireless payment system, initiating a request via a secondcomputer system (e.g., watch, notebook or tablet computer, or the like),or the like.

In some implementations, the second graphical content includes arepresentation of a biometric authentication process (e.g., thegraphical object 2412 in FIG. 24, the graphical object 2516 in FIG. 25,the graphical object 2618 in FIG. 26). For example, in someimplementations, the representation of the biometric authenticationprocess includes an indication that biometric authentication isrequired, an indication that biometric authentication has failed, and/oran indication that biometric authentication has succeeded. In someimplementations, the second graphical content includes an affordance(e.g., the affordance 2512, FIG. 25), and user selection of theaffordance authorizes the wireless payment.

In some implementations, the method further includes, prior to detectingthe occurrence of the event, and in accordance with a determination thatthe case is coupled to the computer system, displaying third graphicalcontent (e.g., the third graphical content 3205 in FIG. 32B, shown as aclock display) in the second region of the display, and in response todetecting the occurrence of the event, reducing a size of the thirdgraphical content. FIG. 32B, for example, shows a reduced-size clockdisplay displayed in the second region of the display in response todetecting an incoming call. In some implementations, a portion of thesecond graphical content is positioned in a portion of the second regionof the display occupied by the third graphical content prior to thereduction in size of the third graphical content (e.g., the reduced-sizeclock display may overlap the area where the initial clock display waspositioned, as shown in FIG. 32B). In some implementations, the thirdgraphical content is a graphical representation of a current time (e.g.,the clock display shown in FIG. 32B).

In some implementations, the second graphical content is a notificationof the event, and the method further includes, after displaying thesecond graphical content (e.g., the graphical content 3106 in FIG. 31),detecting that the computer system is at least partially removed fromthe case such that a third region of the display is not covered by thecase (e.g., region 3108 of the display is not covered by the case, asshown in stage 3103 of FIG. 31), and, in response to detecting that thecomputer system is at least partially removed from the case, displayingthird graphical content (e.g., graphical content 3110) in the thirdregion of the display, the third graphical content includes informationassociated with the event.

In some implementations, the event is an expiration of a timer, and themethod further includes, prior to detecting the occurrence of the event,and in accordance with a determination that the case is coupled to thecomputer system, displaying a progress of the timer in the second regionof the display (e.g., a timer countdown may be shown in the secondregion 2302 (FIG. 23) of a display prior to the expiration of thetimer). In some implementations, the second graphical content includesan affordance (e.g., the affordance 2322 in example 2307 in FIG. 23, thegraphical object 2324 in example 2309 of FIG. 23), and user selection ofthe affordance stops at least one of an audible or a tactile outputtriggered by the expiration of the timer.

In some implementations, the event is a coupling of a charger to thecomputer system, and the second graphical content includes a graphicalrepresentation of a charging function (e.g., the graphical object 2334in example 2313 of FIG. 23, displayed in response to detecting of anattachment of a charging dock to the computer system).

In some implementations, a method includes, at a computer system with adisplay and a housing, while the computer system is operating in a firstmode of operation, detecting a first occurrence of an event, and, inresponse to detecting the first occurrence of the event, displaying, ina first region of the display, first graphical content associated withthe event. The method further includes detecting a coupling of a case tothe computer system, and, in response to detecting the coupling of thecase to the housing of the computer system, transitioning from the firstmode of operation to a second mode of operation. The method furtherincludes while the computer system is operating in the second mode ofoperation and while the case is coupled to the housing of the computersystem, detecting a second occurrence of the event, and, in response todetecting the second occurrence of the event, displaying, in a secondregion of the display different than the first region of the display,second graphical content associated with the event. The first region ofthe display is covered by the case when the case is coupled to thecomputer system, and the second region of the display is visible throughan opening in the case when the case is coupled to the computer system.

FIG. 36 depicts an example schematic diagram of a computer system 3600.The computer system 3600 may correspond to the electronic device 100shown in FIGS. 1A-7 and the electronic devices 800, 802 shown in FIGS.8A-32B. To the extent that multiple functionalities, operations, andstructures are disclosed as being part of, incorporated into, orperformed by the computer system 3600, it should be understood thatvarious embodiments may omit any or all such described functionalities,operations, and structures. Thus, different embodiments of the computersystem 3600 may have some, none, or all of the various capabilities,apparatuses, physical features, modes, and operational parametersdiscussed herein. Further, details of the electronic devices 100, 800,802 that are shown and/or described herein will be understood to applyequally to the computer system 3600. For example, device components(e.g., attachment mechanisms, housings, antennas, etc.), applicationsoftware, graphical user interfaces, etc., may all be embodied by thecomputer system 3600. Further, any of the components, hardware,software, or other systems or components described with respect to thecomputer system 3600 may equally be included in the electronic devices100, 800, and/or 802.

As shown in FIG. 36, a device 3600 includes a processing unit 3602operatively connected to computer memory 3604 and/or computer-readablemedia 3606. The processing unit 3602 may be operatively connected to thememory 3604 and computer-readable media 3606 components via anelectronic bus or bridge. The processing unit 3602 may include one ormore computer processors or microcontrollers that are configured toperform operations in response to computer-readable instructions. Theprocessing unit 3602 may include the central processing unit (CPU) ofthe device. Additionally or alternatively, the processing unit 3602 mayinclude other processors within the device including applicationspecific integrated chips (ASIC) and other microcontroller devices.

The memory 3604 may include a variety of types of non-transitorycomputer-readable storage media, including, for example, read accessmemory (RAM), read-only memory (ROM), erasable programmable memory(e.g., EPROM and EEPROM), or flash memory. The memory 3604 is configuredto store computer-readable instructions, sensor values, and otherpersistent software elements. Computer-readable media 3606 also includesa variety of types of non-transitory computer-readable storage mediaincluding, for example, a hard-drive storage device, a solid-statestorage device, a portable magnetic storage device, or other similardevice. The computer-readable media 3606 may also be configured to storecomputer-readable instructions, sensor values, and other persistentsoftware elements.

In this example, the processing unit 3602 is operable to readcomputer-readable instructions stored on the memory 3604 and/orcomputer-readable media 3606. The computer-readable instructions may beprovided as a computer-program product, software application, or thelike.

As shown in FIG. 36, the computer system 3600 also includes a display3608. The display 3608 may include a liquid-crystal display (LCD),organic light emitting diode (OLED) display, light emitting diode (LED)display, or the like. If the display 3608 is an LCD, the display 3608may also include a backlight component that can be controlled to providevariable levels of display brightness. If the display 3608 is an OLED orLED type display, the brightness of the display 3608 may be controlledby modifying the electrical signals that are provided to displayelements. The display 3608 may correspond to any of the displays shownor described herein, such as the display 104 (FIG. 1A).

The computer system 3600 may also include a battery 3609 that isconfigured to provide electrical power to the components of the computersystem 3600. The battery 3609 may include one or more power storagecells that are linked together to provide an internal supply ofelectrical power. The battery 3609 may be operatively coupled to powermanagement circuitry that is configured to provide appropriate voltageand power levels for individual components or groups of componentswithin the computer system 3600. The battery 3609, via power managementcircuitry, may be configured to receive power from an external source,such as an AC power outlet, a charging dock (e.g., the charging docks200, 804), an auxiliary battery (e.g., the auxiliary battery accessory808), a battery-enabled protective case, or the like. The battery 3609may store received power so that the computer system 3600 may operatewithout connection to an external power source for an extended period oftime, which may range from several hours to several days. Powermanagement circuitry may include wireless charging components, such as acharging coil that inductively couples to an output coil of a wirelesscharger to charge the battery 3609.

In some embodiments, the computer system 3600 includes one or more inputdevices 3610. An input device 3610 is a device that is configured toreceive user input. The one or more input devices 3610 may include, forexample, a rotatable input system, a push button, a touch-activatedbutton, a keyboard, a key pad, or the like (including any combination ofthese or other components). In some embodiments, the input device 3610may provide a dedicated or primary function, including, for example, apower button, volume buttons, home buttons, scroll wheels, and camerabuttons.

The computer system 3600 may also include a sensor 3624. The sensor 3624may detect inputs provided by a user to one or more of the input devices3610 of the computer system 3600. The sensor 3624 may also be abiometric sensor, such as a heart rate sensor, electrocardiographsensor, temperature sensor, or any other type of sensor. In cases wherethe sensor 3624 is a biometric sensor, it may include biometric sensingcircuitry, as well as portions of a crown that conductively couple auser's body to the biometric sensing circuitry. Biometric sensingcircuitry may include components such as processors, capacitors,inductors, transistors, analog-to-digital converters, or the like.

The computer system 3600 may also include a touch sensor 3620 that isconfigured to determine a location of a touch on a touch-sensitivesurface of the computer system 3600 (e.g., an input surface defined bythe transparent cover 105). The touch sensor 3620 may use or includecapacitive sensors, resistive sensors, surface acoustic wave sensors,piezoelectric sensors, strain gauges, or the like. In some cases thetouch sensor 3620 associated with a touch-sensitive surface of thecomputer system 3600 may include a capacitive array of electrodes ornodes that operate in accordance with a mutual-capacitance orself-capacitance scheme. The touch sensor 3620 may be integrated withone or more layers of a display stack (e.g., the display 104, FIG. 1A)to provide the touch-sensing functionality of a touchscreen.

The computer system 3600 may also include a force sensor 3622 that isconfigured to receive and/or detect force inputs applied to a user inputsurface of the computer system 3600 (e.g., a surface of the transparentcover 105). The force sensor 3622 may use or include capacitive sensors,resistive sensors, surface acoustic wave sensors, piezoelectric sensors,strain gauges, or the like. In some cases, the force sensor 3622 mayinclude or be coupled to capacitive sensing elements that facilitate thedetection of changes in relative positions of the components of theforce sensor (e.g., deflections caused by a force input). The forcesensor 3622 may be integrated with one or more layers of a display stack(e.g., the display 104) to provide force-sensing functionality of atouchscreen.

The computer system 3600 may also include a communication port 3628 thatis configured to transmit and/or receive signals or electricalcommunication from an external or separate device. The communicationport 3628 may be configured to couple to an external device via a cable,adaptor, or other type of electrical connector. In some embodiments, thecommunication port 3628 may be used to couple the computer system 3600to an accessory, including a dock or case, a stylus or other inputdevice, smart cover, smart stand, keyboard, or other device configuredto send and/or receive electrical signals.

The computer system 3600 may also include a near-field wirelesscommunication system 3612 (which may correspond to the near-fieldwireless communication system 106 in FIG. 1A). The near-field wirelesscommunication system may include one or more antennas and associatedcircuitry for detecting the presence of near-field wirelesscommunication antennas. The near-field wireless communication system3612 may be configured to operate using any suitable type or protocol ofnear-field wireless communications, including but not limited tonear-field communications (“NFC”) protocols, radio frequencyidentification (“RFID”) protocols, or any other suitable type orprotocol. The near-field wireless communication system 3612 may beconfigured to detect near-field wireless communication antennas througha single side of the device (e.g., the back side), or multiple sides(e.g., any combination of sides including all sides).

While the computer system 3600 is described as having a particular setof components, the computer system 3600 is not limited to only thosecomponents described herein. For example, a device may include more thanone of the components described with respect to FIG. 36 or elsewhere inthe instant application, and may indeed include other components notdescribed herein.

The foregoing description shows and describes various types of graphicalobjects that may be displayed by a device in response to the devicedetecting that it is being used with a near-field wireless enabledaccessory. The graphical objects may take the form of or include icons,graphical user interfaces, background images, notification object (e.g.,for temporary notifications), or the like. The graphical objects may beprogrammatically associated with any suitable application, program, oroperating system of the device, and/or may originate from any suitablelayer of the Open Systems Interconnection model (OSI model). Forexample, in cases where the device detects an accessory and in responsetemporarily displays a notification object over a part of a primarygraphical user interface of an operating system, the notification objectmay be programmatically associated with or originate from the operatingsystem. As another example, in cases where the device detects anaccessory and in response initiates an application, the graphical userinterface of the application may be programmatically associated with ororiginate from the application (where an application may be defined as asoftware program that is executed by or on the operating system).

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve theusefulness of the devices described herein. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter ID's, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used to thebenefit of users. For example, the personal information data can be usedto provide customized graphical user interfaces and user experiences.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure. For instance, healthand fitness data may be used to provide insights into a user's generalwellness, or may be used as positive feedback to individuals usingtechnology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list. Thephrase “at least one of” does not require selection of at least one ofeach item listed; rather, the phrase allows a meaning that includes at aminimum one of any of the items, and/or at a minimum one of anycombination of the items, and/or at a minimum one of each of the items.By way of example, the phrases “at least one of A, B, and C” or “atleast one of A, B, or C” each refer to only A, only B, or only C; anycombination of A, B, and C; and/or one or more of each of A, B, and C.Similarly, it may be appreciated that an order of elements presented fora conjunctive or disjunctive list provided herein should not beconstrued as limiting the disclosure to only that order provided.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the describedembodiments. However, it will be apparent to one skilled in the art thatthe specific details are not required in order to practice the describedembodiments. Thus, the foregoing descriptions of the specificembodiments described herein are presented for purposes of illustrationand description. They are not targeted to be exhaustive or to limit theembodiments to the precise forms disclosed. It will be apparent to oneof ordinary skill in the art that many modifications and variations arepossible in view of the above teachings. Also, when used herein to referto positions of components, the terms above and below, or theirsynonyms, do not necessarily refer to an absolute position relative toan external reference, but instead refer to the relative position ofcomponents with reference to the figures.

What is claimed is:
 1. A method, comprising: at a computer system with adisplay, a housing, and an attachment mechanism: detecting attachment ofan accessory to the computer system, where the accessory, whileattached, has a predetermined orientation relative to the attachmentmechanism; and in response to detecting the attachment of the accessoryto the computer system: in accordance with a determination that theaccessory is a first accessory with first physical dimensions,displaying, on the display, a first visual indication that the accessoryhas been attached to the computer system, wherein the first visualindication indicates at least one property of the first physicaldimensions; and in accordance with a determination that the accessory isa second accessory with second physical dimensions that are differentfrom the first physical dimensions, displaying, on the display a secondvisual indication that the accessory has been attached to the computersystem, wherein:  the second visual indication indicates at least oneproperty of the second physical dimensions; and  the second visualindication is different from the first visual indication.
 2. The methodof claim 1, wherein the attachment mechanism is a magnetic attachmentmechanism.
 3. The method of claim 1, wherein the first accessory has afirst shape and the second accessory has a second shape, and the firstvisual indication has a first graphical element having the first shapeand the second visual indication has a second graphical element havingthe second shape.
 4. The method of claim 3, wherein the first accessoryhas a first size and the second accessory has a second size, and thefirst visual indication has the first size and the second visualindication has the second size.
 5. The method of claim 1, wherein thefirst accessory is shorter than the second accessory in a respectivedimension, and the first visual indication is shorter than the secondvisual indication in the respective dimension.
 6. The method of claim 5,wherein: the first visual indication occupies less than an entire areaof the display; and the second visual indication occupies an entire areaof the display.
 7. The method of claim 6, wherein the second accessoryis a protective case for the computer system.
 8. The method of claim 1,wherein the first visual indication and the second visual indicationinclude at least one common element.
 9. The method of claim 8, whereinthe at least one common element is displayed at a location thatcorresponds to a location of the attachment mechanism in the computersystem.
 10. The method of claim 8, wherein the at least one commonelement is displayed in a shape that corresponds to a shape of theattachment mechanism in the computer system.
 11. The method of claim 1,further comprising, while the accessory is attached to the computersystem: detecting attachment of an additional accessory to the computersystem, where the additional accessory, while attached, has apredetermined orientation relative to the attachment mechanism; and inresponse to detecting the attachment of the additional accessory to thecomputer system and in accordance with a determination that theadditional accessory is a third accessory with third physicaldimensions, displaying, on the display, a third visual indicationindicating that the additional accessory has been attached to thecomputer system, wherein the third visual indication indicates at leastone property of the third physical dimensions and is different from thefirst visual indication and the second visual indication.
 12. The methodof claim 1, wherein: the method further comprises displaying, on thedisplay, a graphical user interface; and the first visual indicationoverlies at least a portion of the graphical user interface.
 13. Themethod of claim 12, wherein: the first visual indication is atranslucent graphical object; and at least a portion of the graphicaluser interface is visible through the translucent graphical object. 14.The method of claim 1, further comprising: in accordance with adetermination that the computer system is in a first state when theattachment of the accessory is detected: displaying the first visualindication in accordance with the determination that the accessory isthe first accessory; and displaying the second visual indication inaccordance with the determination that the accessory is the secondaccessory; and in accordance with a determination that the computersystem is in a second state, different from the first state, when theattachment of the accessory is detected, forgoing display of the firstvisual indication and/or the second visual indication.
 15. The method ofclaim 1, wherein the first visual indication and the second visualindication include information associated with the accessory.
 16. Themethod of claim 1, further comprising, in response to detecting theattachment of the accessory to the computer system, producing anon-visual output, wherein the non-visual output is produced inaccordance with the determination that the accessory is the firstaccessory and in accordance with the determination that the accessory isthe second accessory.
 17. The method of claim 16, wherein: the firstaccessory is a first type of accessory; the second accessory is a secondtype of accessory different from the first type of accessory; and thesame non-visual output is produced by the computer system when the firstaccessory is attached to the computer system and when the secondaccessory is attached to the computer system.
 18. The method of claim 1,wherein the second visual indication is different from the first visualindication in a manner that indicates a difference between the firstphysical dimensions and the second physical dimensions.
 19. The methodof claim 1, wherein the first visual indication comprises a respectiveportion that expands outward from a location that corresponds to alocation of the attachment mechanism in the computer system.
 20. Themethod of claim 1, wherein the accessory is at least one of: a chargingdock; a wallet accessory; a protective case; and an auxiliary batteryfor charging the computer system.
 21. The method of claim 1, furthercomprising: detecting detachment of the accessory from the computersystem; and in response to detecting the detachment: in accordance witha determination that the accessory is a first type of accessory,generating a first type of detach output; and in accordance with adetermination that the accessory is a second type of accessory, forgoinggeneration of the detach output.
 22. The method of claim 1, furthercomprising: detecting detachment of the accessory from the computersystem; and in response to detecting the detachment, producing a detachoutput indicating that the accessory has been detached from the computersystem.
 23. The method of claim 21, wherein the detach output includesnon-visual output.
 24. The method of claim 21, the detach outputincludes a visual detach indication.
 25. The method of claim 24,wherein: the first visual indication is an animated visual indication;the second visual indication is an animated visual indication; anddisplaying the visual detach indication includes: in accordance with adetermination that the accessory is the first accessory, displaying athird visual indication that includes a reversal of at least a portionof (or all of) the first visual indication; and in accordance with adetermination that the accessory is the second accessory, displaying afourth visual indication that is different from the third visualindication and that includes a reversal of at least a portion of (or allof) the second visual indication.
 26. A method, comprising: at acomputer system with a display and a housing: displaying a firstgraphical user interface comprising: first graphical content displayedin a first region of the display; and second graphical content displayedin a second region of the display, the second region different than thefirst region; detecting a coupling of a case to the computer system,wherein: the first region of the display is covered by the case; and thesecond region of the display is visible through an opening in the case;and in response to detecting the coupling of the case to the computersystem, transitioning from displaying the first graphical user interfaceto a second graphical user interface, the transitioning comprising:ceasing to display the second graphical content in the second region ofthe display; and displaying the second graphical user interface on thedisplay, the second graphical user interface comprising third graphicalcontent, different from the second graphical content, displayed in thesecond region of the display.
 27. The method of claim 26, wherein thesecond graphical content of the second graphical user interfacecomprises: a background graphic; and a foreground graphic on thebackground graphic.
 28. The method of claim 27, wherein: the backgroundgraphic has a first color that matches a color of the case; and theforeground graphic has a second color different than the first color.29. The method of claim 27, wherein: the background graphic initiallyhas a first color that matches a color of the case; the foregroundgraphic initially has a second color different from the first color; anddisplaying the second graphical user interface comprises, afterdisplaying the background graphic having the first color and theforeground graphic having the second color, transitioning the backgroundgraphic from the first color to a third color.
 30. The method of claim29, further comprising, after displaying the background graphic havingthe first color and the foreground graphic having the second color,transitioning the foreground graphic from the second color to the firstcolor.
 31. The method of claim 26, wherein the transition furthercomprises, prior to displaying the second graphical user interface,displaying a black background graphic in the second region of thedisplay.
 32. The method of claim 26, further comprising, while the caseis coupled to the computer system: detecting an occurrence of an event;and in response to detecting the occurrence of the event, displaying, inthe second region of the display, a graphical object associated with theevent.
 33. The method of claim 32, wherein: the event is an incomingcall; and the graphical object comprises an accept-call affordance. 34.The method of claim 33, further comprising: detecting a selection of theaccept-call affordance; and in response to detecting the selection ofthe accept-call affordance: accepting the incoming call; and displayingan audio selection affordance and an end-call affordance.
 35. The methodof claim 32, wherein the event is a user request to initiate a wirelesspayment.
 36. The method of claim 35, wherein the graphical objectcomprises a representation of a payment card associated with thewireless payment.
 37. The method of claim 35, wherein the graphicalobject comprises a representation of a biometric authentication process.38. The method of claim 35, wherein: the graphical object comprises anaffordance; and user selection of the affordance authorizes the wirelesspayment.
 39. The method of claim 32, wherein the event is a notificationof a received message.
 40. The method of claim 32, wherein the event isa coupling of a charger to the computer system.
 41. The method of claim32, wherein: the event is an initiation of a voice-based digitalassistant; and the graphical object is animated in accordance with avoice input received by the computer system.
 42. The method of claim 32,wherein: the event is an expiration of a timer; the graphical objectcomprises an affordance; and user selection of the affordance stops atleast one of an audible or a tactile output triggered by the expirationof the timer.
 43. The method of claim 26, further comprising: detectinga gesture on the second graphical user interface; and in response todetecting the gesture, displaying fourth graphical content, differentfrom the third graphical content, in the second region of the display.44. The method of claim 43, wherein: the gesture is a first gesture; andthe method further comprises: detecting a second gesture on the secondgraphical user interface; and in response to detecting the secondgesture, displaying fifth graphical content, different from the fourthgraphical content, in the second region of the display.
 45. The methodof claim 44, wherein: the first gesture is a swipe in a first direction;the fourth graphical content comprises a plurality of affordances; thesecond gesture is a swipe in a second direction opposite the firstdirection; and the fifth graphical content comprises a set of mediaplayback controls.
 46. The method of claim 43, wherein the fourthgraphical content comprises a plurality of affordances.
 47. The methodof claim 46, wherein the plurality of affordances comprise a firstaffordance and a second affordance, and the method further comprises:detecting a gesture initiated on the first affordance; and in responseto detecting the gesture, replacing the first affordance with a thirdaffordance different than the first affordance.
 48. A method,comprising: at a computer system with a display and a housing: detectingan occurrence of an event; and in response to detecting the occurrenceof the event: in accordance with a determination that a case is notcoupled to the computer system, displaying, in a first region of thedisplay, first graphical content associated with the event; and inaccordance with a determination that the case is coupled to the computersystem, displaying, in a second region of the display different than thefirst region of the display, second graphical content associated withthe event, wherein: the first region of the display is covered by thecase when the case is coupled to the computer system; and the secondregion of the display is visible through an opening in the case when thecase is coupled to the computer system.
 49. The method of claim 48,wherein: the event is an incoming call; and the second graphical contentcomprises an accept-call affordance.
 50. The method of claim 49, furthercomprising: detecting a selection of the accept-call affordance; and inresponse to detecting the selection of the accept-call affordance:accepting the incoming call; and displaying an audio selectionaffordance and an end-call affordance.
 51. The method of claim 49,wherein the second graphical content comprises a scrolling textincluding information about the incoming call.
 52. The method of claim48, wherein the first graphical content is different than the secondgraphical content.
 53. The method of claim 52, wherein: the firstgraphical content comprises a first affordance having a firstappearance; the second graphical content comprises a second affordancehaving a second appearance; user selection of the first affordancecauses the computer system to perform an action; and user selection ofthe second affordance causes the computer system to perform the action.54. The method of claim 48, wherein the event is a user request toinitiate a wireless payment.
 55. The method of claim 54, wherein thesecond graphical content comprises a representation of a payment cardassociated with the wireless payment.
 56. The method of claim 54,wherein the second graphical content comprises a representation of abiometric authentication process.
 57. The method of claim 54, wherein:the second graphical content comprises an affordance; and user selectionof the affordance authorizes the wireless payment.
 58. The method ofclaim 48, wherein: the method further comprises: prior to detecting theoccurrence of the event, and in accordance with a determination that thecase is coupled to the computer system, displaying third graphicalcontent in the second region of the display; and in response todetecting the occurrence of the event, reducing a size of the thirdgraphical content; and a portion of the second graphical content ispositioned in a portion of the second region of the display occupied bythe third graphical content prior to the reduction in size of the thirdgraphical content.
 59. The method of claim 58, wherein the thirdgraphical content is a graphical representation of a current time. 60.The method of claim 48, wherein: the second graphical content is anotification of the event; and the method further comprises: afterdisplaying the second graphical content, detecting that the computersystem is at least partially removed from the case such that a thirdregion of the display is not covered by the case; and in response todetecting that the computer system is at least partially removed fromthe case, displaying third graphical content in the third region of thedisplay, the third graphical content comprises information associatedwith the event.
 61. The method of claim 48, wherein: the event is anexpiration of a timer; and the method further comprises prior todetecting the occurrence of the event, and in accordance with adetermination that the case is coupled to the computer system,displaying a progress of the timer in the second region of the display;the second graphical content comprises an affordance; and user selectionof the affordance stops at least one of an audible or a tactile outputtriggered by the expiration of the timer.
 62. The method of claim 48,wherein: the event is a coupling of a charger to the computer system;and the second graphical content comprises a graphical representation ofa charging function.
 63. A method, comprising: at a computer system witha display and a housing: while the computer system is operating in afirst mode of operation: detecting a first occurrence of an event; andin response to detecting the first occurrence of the event, displaying,in a first region of the display, first graphical content associatedwith the event; detecting a coupling of a case to the computer system;in response to detecting the coupling of the case to the housing of thecomputer system, transitioning from the first mode of operation to asecond mode of operation; and while the computer system is operating inthe second mode of operation and while the case is coupled to thehousing of the computer system: detecting a second occurrence of theevent; and in response to detecting the second occurrence of the event,displaying, in a second region of the display different than the firstregion of the display, second graphical content associated with theevent, wherein: the first region of the display is covered by the casewhen the case is coupled to the computer system; and the second regionof the display is visible through an opening in the case when the caseis coupled to the computer system.